Skip site navigation (1) Skip section navigation (2)

Re: Enforcing database encoding and locale match

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Enforcing database encoding and locale match
Date: 2007-10-01 17:06:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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                      
The PostgreSQL Company - Command Prompt, Inc.

In response to


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group