Re: tsearch parser overhaul

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> 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?:
> http://vo.astronet.ru/arxiv/dict_regex.html
> I suspect we'd need to get it to use the same regexp code used
> elsewhere in PostgreSQL.

We're certainly not going to start carrying two regexp engines,
so yeah ;-)

I guess if this is proposed as a replacement for the existing parser,
we'd need to see some speed comparisons.  I have no idea at all which
is faster.
        regards, tom lane