Re: Need help with full text index configuration

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Brian Hirt <bhirt(at)mobygames(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Need help with full text index configuration
Date: 2010-07-28 20:06:50
Message-ID: 22244.1280347610@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> For example instead of the parser recognizing three asciiword it recognizes one asciiword and one file. I'd like a way to have the / just get parsed as blank.

AFAIK the only good way to do that is to write your own parser :-(.
The builtin parser isn't really configurable. (If you didn't mind
maintaining a private version you could patch its state transition
table manually, but that seems like a PITA.)

For the case at hand it could be a pretty thin frontend to the builtin
text parser --- just change / to space and then call the builtin one.
contrib/test_parser/ might help you get started.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message raghu ram 2010-07-28 20:12:19 Pglesslog issue
Previous Message Peter Bex 2010-07-28 19:48:53 Re: How Big is Too Big for Tables?