tsearch parser overhaul

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgresql(dot)org>
Cc: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Andres Freund" <andres(at)anarazel(dot)de>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>,<teodor(at)sigaev(dot)ru>
Subject: tsearch parser overhaul
Date: 2009-12-10 21:02:54
Message-ID: 4B210D9E020000250002D344@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Kevin Grittner wrote:
>> (Note: I personally would much rather see the performance
>> penalty addressed this way, and a TODO added for the more
>> invasive work, than to leave this alone for the next release if
>> there's nobody willing to tackle the problem at a more
>> fundamental level.)
> +1

I haven't added a TODO yet because I'm not sure how to frame it.
I'm inclined that it would be no more work to replace the current
recursively called state engine with something easier to read and
understand than to try to fix the current oddities. Perhaps
something along the lines of this?:


I suspect we'd need to get it to use the same regexp code used
elsewhere in PostgreSQL.



In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-12-10 21:26:48 Re: Adding support for SE-Linux security
Previous Message Alvaro Herrera 2009-12-10 20:58:55 Re: XLogInsert