Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane? - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?
Date
Msg-id 87r6lwhsuj.fsf@oxford.xeocode.com
Whole thread Raw
In response to Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> After starting to document this stuff I'm wondering whether it really
> makes sense to change the parser associated with a tsearch
> configuration.  The problem is that the new parser might have an
> unrelated set of token types, but we don't do anything about updating
> the configuration's mappings.

I'm not really up-to-date on all this tsearch stuff. What would happen if you
already had a parser but wanted to fix a bug or add one new feature or
something like that?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: tsearch2 patch status report
Next
From: Andrew Dunstan
Date:
Subject: Re: tsearch2 patch status report