Postgres Pro
Downloads
Home   >   mailing lists

Re: Enforcing database encoding and locale match - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Enforcing database encoding and locale match
Date
Msg-id 18185.1191259353@sss.pgh.pa.us
Whole thread Raw
In response to Re: Enforcing database encoding and locale match  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Enforcing database encoding and locale match
List pgsql-hackers
Tree view 
Alvaro Herrera <alvherre@commandprompt.com> writes:
> FWIW I tried this program here, and I get

> C                       ... ANSI_X3.4-1968 - NO MATCH
> POSIX                   ... ANSI_X3.4-1968 - NO MATCH

> Note the funny name.  Trying initdb with LC_ALL=C correctly uses
> SQL_ASCII (I saw the special case in chklocale.c), but I'm wondering if
> we should list those names explicitely.

Since we're already special-casing C/POSIX, I don't see a need.
It looks a bit hopeless to keep up with all the possibilities anyway
--- by my count we've tested four different platforms so far and
gotten four different answers for the CODESET name for C :-(

Linux    ANSI_X3.4-1968
Darwin    (empty)
Solaris    646
HP-UX    roman8
        regards, tom lane

pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: First steps with 8.3 and autovacuum launcher
Next
From: Tom Lane
Date:
Subject: Re: PG on NFS may be just a bad idea