Skip site navigation (1) Skip section navigation (2)

Re: tsearch Parser Hacking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tsearch Parser Hacking
Date: 2011-02-14 23:57:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> Is it possible to modify the default tsearch parser so that / doesn't get lexed as a "file" token?

There is zero, none, nada, provision for modifying the behavior of the
default parser, other than by changing its compiled-in state transition

It doesn't help any that said tables are baroquely designed and utterly

IMO, sooner or later we need to trash that code and replace it with
something a bit more modification-friendly.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2011-02-15 00:00:18
Subject: Re: why two dashes in extension load files
Previous:From: Robert HaasDate: 2011-02-14 23:55:22
Subject: Re: CommitFest 2011-01 as of 2011-02-04

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group