Re: Strange query results with invalid multibyte - Mailing list pgsql-general

From Joost Kraaijeveld
Subject Re: Strange query results with invalid multibyte
Date
Msg-id 1159373085.29038.11.camel@panoramix
Whole thread Raw
In response to Re: Strange query results with invalid multibyte character  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Strange query results with invalid multibyte character
List pgsql-general
Hi Tom,

On Wed, 2006-09-27 at 11:00 -0400, Tom Lane wrote:
> "Joost Kraaijeveld" <J.Kraaijeveld@Askesis.nl> writes:
> > I have 2 database, both created with:
> > CREATE DATABASE muntdev WITH OWNER = postgres ENCODING = 'UTF8' TABLESPACE = pg_default;
>
> But have they got the same locale settings (lc_collate, lc_ctype)?

According to the postgresql.conf of the *working* database the locales
are:
lc_messages = 'C'
lc_monetary = 'C'
lc_numeric = 'C'
lc_time = 'C'

According to the other obe:
lc_messages = 'en_US'
lc_monetary = 'en_US'
lc_numeric = 'en_US'
lc_time = 'en_US'


Could this be the difference? Is there any documentation available
somewhere, on how these locale settings work and  interact (in
combination with the server and/or client platform???), besides the
explanation in the PostgreSQL manual
(http://www.postgresql.org/docs/8.1/interactive/charset.html#LOCALE)
(which is to terse for me to understand)?

TIA


--
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: File System Access:
Next
From: Tom Lane
Date:
Subject: Re: Strange query results with invalid multibyte character