Re: Encoding problem with 7.4

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: "E(dot)Rodichev" <er(at)sai(dot)msu(dot)su>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Encoding problem with 7.4
Date: 2003-12-03 16:07:20
Message-ID: 20031203080200.P28610@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Wed, 3 Dec 2003, E.Rodichev wrote:

> On Fri, 28 Nov 2003, Tom Lane wrote:
>
> > "E.Rodichev" <er(at)sai(dot)msu(dot)su> writes:
> > > /e:2>createdb test
> >
> > > test | er | SQL_ASCII <----- Incorrect!
> > > (3 rows)
> >
> > > Let's note than the last line is in fact completely incorrect.
> >
> > What's incorrect about it? You didn't ask for any other encoding
> > than SQL_ASCII.
>
> It is incorrect, because database "test" is, really, in KOI8, NOT in SQL_ASCII
> in this example, as I explained in my mail.

No, it isn't. As far as PostgreSQL is concerned the database is SQL_ASCII
since you didn't override the default encoding at initdb time or at
createdb time. You did choose LC_ values that seem to want KOI8, but
locale and encoding are separate, if you want KOI8 encoding, you have to
say so.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Anand, VJ (MED, GEMS-IT) 2003-12-03 16:18:52 BTree index and optimizer
Previous Message Andrew Dunstan 2003-12-03 15:47:34 Re: Inside the Regex Engine