From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | Behdad Esfahbod <behdad(at)bamdad(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Setting locale per connection |
Date: | 2003-07-02 05:58:57 |
Message-ID: | 24946.1057125537@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> On Wed, 2 Jul 2003, Behdad Esfahbod wrote:
>> so I have wrote my 10lines function as a wrapper around
>> setlocale, that is attached.
> Hmm, I'd think there'd be some potential for danger there. I don't play
> with the locale stuff, but if the collation changes and you've got indexed
> text (varchar, char) fields, wouldn't the index no longer necessarily be
> in the correct order?
Indeed, this is exactly why Postgres goes out of its way to prevent you
from changing the backend's collation setting on-the-fly. The proposed
function is a great way to shoot yourself in the foot :-(. If you doubt
it, check the archives from two or three years ago when we did not have
the interlock to force LC_COLLATE to be frozen at initdb time ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kenji Sugita | 2003-07-02 06:49:19 | PostgreSQL 7.4devel - LOG: PGSTAT: socket() failed: Invalid argument |
Previous Message | Craig Jensen | 2003-07-02 05:20:57 | help with rpm script |