Re: tsearch Parser Hacking - Mailing list pgsql-hackers

From Thom Brown
Subject Re: tsearch Parser Hacking
Date
Msg-id AANLkTi=YsMnssRQUNodKQ59xudzV+S0Dr3PkgoSwOaLw@mail.gmail.com
Whole thread Raw
In response to Re: tsearch Parser Hacking  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 14 February 2011 23:57, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "David E. Wheeler" <david@kineticode.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
> tables.
>
> It doesn't help any that said tables are baroquely designed and utterly
> undocumented.

This is very true. I intended to look into adding new tokens, but gave
up when I couldn't see how those transition tables worked.

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

+1 for annihilating the existing code at some point.

-- 
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: why two dashes in extension load files
Next
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,