Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

• Re: Enforcing database encoding and locale match at 2007-10-01 17:06:58 from Alvaro Herrera

Responses

• Re: Enforcing database encoding and locale match at 2007-10-05 20:10:45 from Zdenek Kotala

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2007-10-01 17:24:41
	Subject: Re: [HACKERS] PG on NFS may be just a bad idea
Previous:	From: Islam Hegazy	Date: 2007-10-01 17:17:47
	Subject: Re: adding operators