| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | grzm(at)seespotcode(dot)net, teodor(at)sigaev(dot)ru, bruce(at)momjian(dot)us, hannu(at)skype(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsearch in core patch |
| Date: | 2007-06-22 16:38:14 |
| Message-ID: | 23565.1182530294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
>> On Jun 22, 2007, at 9:28 , Tom Lane wrote:
>>> Is the point here for initdb to be able to establish a sane default
>>> initially? Seems to me it can guess the language from the first
>>> component of the locale (ru_RU -> russian).
>>
>> How would this work for initdb with locale C?
> I'm worrying about that too.
I would be surprised if C locale defaulted to anything except English.
I suppose it would be sensible to add a switch to allow people to select
a different language. In any case, the only thing initdb would be doing
would be setting up an initial value of a table entry or GUC variable,
so you could always change it yourself later; it may not be worth
sweating too much about this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-22 17:30:54 | Re: Worries about delayed-commit semantics |
| Previous Message | Tatsuo Ishii | 2007-06-22 16:26:08 | Re: [Fwd: Re: tsearch in core patch] |