From: | Rob van Nieuwkerk <robn(at)verdi(dot)et(dot)tudelft(dot)nl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rob van Nieuwkerk <robn(at)verdi(dot)et(dot)tudelft(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.0.3 reproduceable serious select error |
Date: | 2001-01-18 23:15:10 |
Message-ID: | 200101182315.AAA01433@verdi.et.tudelft.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> > I don't think I'm running postmaster in a non-ASCII locale.
> > At least I did not explicitly do anything to accomplish it.
>
> Did you have LANG, LOCALE, or any of the LC_xxx family of
> environment variables set when you started the postmaster?
> Some Linux distros tend to set those in system profile scripts ...
Checking whith ps and looking in /proc reveiled that postmaster indeed
had LANG set to "en_US" in its environment. I disabled the system script
that makes this setting, restarted postgres/postmaster and reran my tests.
The problem query returns the *right* answer now !
Turning LANG=en_US back on gives the old buggy behaviour.
I know very little about this LANG, LOCALE etc. stuff.
But for our application it is very important to support "weird" characters
like " ..." etc. for names. Basically we need all letter symbols
in ISO-8859-1 (Latin 1). A quick experiment shows that without the
LANG setting I can still insert & select strings containing these
symbols.
Do I lose any postgresql functionality by just getting rid of the LANG
environment variable ? Will I be able to use full ISO-8859-1 in table
fields without problems ?
Please tell if you want me to do any other tests !
greetings,
Rob van Nieuwkerk
From | Date | Subject | |
---|---|---|---|
Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-01-18 23:41:43 | Re: 7.0.3 reproduceable serious select error |
Previous Message | Nathan Myers | 2001-01-18 22:27:09 | Re: copy from stdin; bug? |