On Tue, Oct 26, 2010 at 8:46 PM, Josh Kupershmidt wrote:
> It looks like effective_io_concurrency only has an impact on bitmap
> heap scans. I think a brief mention of this fact in the docs for
> effective_io_concurrency should suffice, patch attached.
Good idea, committed.
--
Robert Haas
Enter
t...@sss.pgh.pa.us wrote:
> I think we should simply remove the description of *how* the escaping is
> performed, and state only that the function produces a suitably escaped
> literal string. Anything else is not future-proof, and could someday
> break the way this wording did.
Perhaps it would
[moving to -docs]
On Wed, Oct 20, 2010 at 10:30 PM, Bruce Momjian wrote:
> Josh Kupershmidt wrote:
>> But it looks to me like effective_io_concurrency only affects bitmap
>> heap scans. The setting from effective_io_concurrency gets put into
>> "target_prefetch_pages" in ./src/backend/utils/misc/
Hi,
I'd like to build a custom text search parser and then use it within a
custom text search configuration.
It would be great if you could give us an example showing how to build a
custom parser, including examples of start, gettoken and end functions.
It would be even greater if one could add cus
