| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paesold <mpaesold(at)gmx(dot)at>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How does the tsearch configuration get selected? |
| Date: | 2007-06-15 14:26:53 |
| Message-ID: | 200706151426.l5FEQr601745@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Bruce Momjian wrote:
> My guess right now is that we use a GUC that will default if a
> pg_catalog configuration name matches the lc_ctype locale name, and we
> have to throw an error if an accessed index creation GUC doesn't match
> the current GUC.
>
> So we create a pg_catalog full text configuration named UTF8.en-US, and
> some others like ru_RU.UTF-8.
Do locale names vary across operating systems? If so, we might as well
skip trying to find a default.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 14:36:15 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Bruce Momjian | 2007-06-15 14:15:31 | Re: How does the tsearch configuration get selected? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 14:36:15 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Bruce Momjian | 2007-06-15 14:15:31 | Re: How does the tsearch configuration get selected? |