From: | "Florian G(dot) Pflug" <fgp(at)master(dot)phlo(dot)org> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tsearch_core for inclusion |
Date: | 2007-03-23 12:49:42 |
Message-ID: | 4603CCE6.8090800@master.phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Teodor Sigaev wrote:
> For given schema and server's locale, it's possible to have several FTS
> configurations, but the only one (with special flag enabled)
> could be used as default. Current (active) FTS configuration contains
> in GUC variable tsearch_conf_name. If it's not defined, then FTS
> configuration
> is looked in search_path to match server's locale with default flag
> enabled.
Isn't the real problem that only _one_ configuration per locale should
be marked as DEFAULT at any time, no matter what schema it is in?
Having one DEFAULT configuration per schema per locale will necessarily
cause confusion if search_path is not set carefully I think.
greetings, Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2007-03-23 12:51:28 | Re: CREATE INDEX and HOT - revised design |
Previous Message | Teodor Sigaev | 2007-03-23 11:58:10 | tsearch_core for inclusion |