Re: Encoding problem with 7.4 - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: Encoding problem with 7.4
Date
Msg-id 20031204073747.U66123@megazone.bigpanda.com
Whole thread Raw
In response to Re: Encoding problem with 7.4  ("E.Rodichev" <er@sai.msu.su>)
List pgsql-hackers
On Thu, 4 Dec 2003, E.Rodichev wrote:

> On Wed, 3 Dec 2003, Stephan Szabo wrote:
>
> > The locale settings depend on LC_* at initdb time only. When the
> > postmaster starts it sets the locale based on the stored values from
> > initdb, not on the current environment.
> >
> > With an SQL_ASCII database being accessed from a client with
> > client_encoding set to SQL_ASCII (which it should be if you aren't setting
> > it) the byte values of a string are passed along with no conversion for
> > the encoding.  This means that from within one environment you should get
> > back what you put in, so it might *look* like it's KOI8-R if that's what
> > you're in, but it's not because someone accessing it from say an ISO8859-1
> > system may see something different.
>
> As a result, the possibility to control encodings and locales looks as
> follows:
>
>             initdb   createdb     psql
> Encoding:      Y         Y          Y

As a note you can change the *client* encoding from psql, not the *server*
encoding.  They're also two separate notions.

Andrew already commented on the TODO list.  You may also wish to look
through the archives for a recent message from Peter E on the subject as
he was looking into starting towards multiple collations and such.


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Encoding problem with 7.4
Next
From: "phd9110"
Date:
Subject: Does Catalog contain the information of index insert/update/delete tuples number ??