From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tsearch Parser Hacking |
Date: | 2011-02-15 00:02:02 |
Message-ID: | AANLkTi=YsMnssRQUNodKQ59xudzV+S0Dr3PkgoSwOaLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 14 February 2011 23:57, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-02-15 00:21:31 | Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
Previous Message | Robert Haas | 2011-02-15 00:00:18 | Re: why two dashes in extension load files |