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

From Oleg Bartunov
Subject Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?
Date
Msg-id Pine.LNX.4.64.0708220753060.2727@sn.sai.msu.ru
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
On Tue, 21 Aug 2007, Tom Lane wrote:

> 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.

looks reasonable, we could always create new parser.

>
> Ensuring sane behavior here would take a whole lot of new code, and
> I'm not sure that I see a use-case that justifies it.  So I'm tempted to
> take out that particular ALTER capability altogether.  I note that the
> corresponding feature of changing a dictionary's template on-the-fly
> doesn't exist (though it'd actually be a lot easier to support).

yes, here we tried to be sane

>
> Comments?


    Regards,        Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: tsearch2 patch status report
Next
From: Tom Lane
Date:
Subject: Re: Crash with empty dictionary