Tom Lane wrote:

> I tried this program on Mac OS X 10.4.10 (the current release) and found
> out that what that OS mostly returns is the encoding portion of the
> locale name, for instance

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.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

• Re: Enforcing database encoding and locale match at 2007-09-28 22:58:53 from Tom Lane

Responses

• Re: Enforcing database encoding and locale match at 2007-10-01 17:22:33 from Tom Lane

pgsql-hackers by date

Next:	From: Josh Berkus	Date: 2007-10-01 17:13:41
	Subject: Re: [HACKERS] PG on NFS may be just a bad idea
Previous:	From: Dimitri Fontaine	Date: 2007-10-01 16:20:21
	Subject: Re: IDE