Re: Locale bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sergey Suleymanov <solt(at)eatpbank(dot)ru>
Cc: pgsql-general(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Locale bug?
Date: 2003-10-14 05:56:02
Message-ID: 6683.1066110962@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sergey Suleymanov <solt(at)eatpbank(dot)ru> writes:
> Tom Lane writes:
>>> ... That is upper() doesn't work correctly after plperlu function
>>> call.

> Tom> It sounds like Perl is taking it on itself to change the
> Tom> process' LC_CTYPE settings. That's very nasty of it :-(. Can
> Tom> anyone confirm that libperl does such things, or find a
> Tom> workaround to prevent it?

> It seems a startup script issue. When I restarting postmaster
> manualy (within root session with LC_CTYPE = ru_RU.KOI8-R)
> everything works fine.

> Do we need "export LANG=..." before starting postmaster?

Hm. The postmaster extracts the correct setlocale() values from the
pg_control file, but IIRC it doesn't bother to set the environment
variables LC_CTYPE etc. Maybe it should. Peter, I think this is your
turf --- what do you think?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message B.W.H. van Beest 2003-10-14 09:53:21 How to list which tables are available?
Previous Message Mike Mascari 2003-10-14 05:23:56 Re: SET within a function?