| 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:42:26 |
| Message-ID: | 22887.1280349746@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:
> I'm really confused about what "ALTER TEXT SEARCH CONFIGURATION dict DROP MAPPING FOR file" actually does. The documentation seems to make it sound like it does what I want, but I guess it does something else.
No, it doesn't affect the parser's behavior at all. So foo/bar will
still be parsed as a "file" token. What the above results in is
dropping file tokens on the floor afterwards, instead of passing them
to some dictionary. In general the mapping stuff just controls what
dictionary(s) tokens produced by the parser will be routed to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J. Greg Davidson | 2010-07-28 21:27:16 | Danger of idiomatic plpgsql loop for merging data |
| Previous Message | Brian Hirt | 2010-07-28 20:19:31 | Re: Need help with full text index configuration |