Bruce Momjian wrote:
>
> Added to TODO:
>
> * Add SHOW command to see locale
I'd rather like it to be a function, as version() is, because SHOW
commands may not
play nice with other interfaces than psql.
(and it can first be included in ./contrib if it's too late for a
"feature" )
Ju
Rob van Nieuwkerk wrote:
>
>
> 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 "éőĺĘ ..."
Added to TODO:
* Add SHOW command to see locale
> Barry Lind <[EMAIL PROTECTED]> writes:
> > I meant to ask this the last time this came up on the list, but now is a
> > good time. Given what Tom describes below as the behavior in 7.1
> > (initdb stores the locale info), how do you dete
Barry Lind <[EMAIL PROTECTED]> writes:
> I meant to ask this the last time this came up on the list, but now is a
> good time. Given what Tom describes below as the behavior in 7.1
> (initdb stores the locale info), how do you determine what locale a
> database is running in in 7.1 after initdb?
I meant to ask this the last time this came up on the list, but now is a
good time. Given what Tom describes below as the behavior in 7.1
(initdb stores the locale info), how do you determine what locale a
database is running in in 7.1 after initdb? Is there some file to look
at? Is there some
Rob van Nieuwkerk <[EMAIL PROTECTED]> writes:
> 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 retur
Rob van Nieuwkerk <[EMAIL PROTECTED]> writes:
> 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).
en_US is latin1
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
> 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 s
Tom Lane wrote:
>
> [EMAIL PROTECTED] (Rob van Nieuwkerk) writes:
> > The problem is that a SELECT with a certain LIKE condition in combination
> > with a GROUP BY does not find the proper records when there is an index on
> > the particular column present. When the index is removed the SELECT *
[EMAIL PROTECTED] (Rob van Nieuwkerk) writes:
> The problem is that a SELECT with a certain LIKE condition in combination
> with a GROUP BY does not find the proper records when there is an index on
> the particular column present. When the index is removed the SELECT *does*
> return the right an
11 matches
Mail list logo
