| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Hannu Krosing <hannu(at)skype(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tsearch in core patch |
| Date: | 2007-06-27 14:14:33 |
| Message-ID: | 16095.1182953673@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> But why do you need them to be different at all? Just make it
>> russian Russian_Russia
>> russian ru_RU
>>
>> Does that not work for some reason?
> I'd like to have unique names of configuration. So, if user sets GUC variable or
> call function with configuration's name then postgres should not have a choice
> --- it should use pointed configuration exactly.
Sure, but the configuration name in this example is "russian", and it's
unique, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-27 14:38:54 | Re: Bgwriter LRU cleaning: we've been going at this all wrong |
| Previous Message | Tom Lane | 2007-06-27 14:12:53 | Re: Frustrating issue with PGXS |