Re: New database: SQL_ASCII vs UTF-8 trade-offs

From: ow <oneway_111(at)yahoo(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs
Date: 2006-03-07 16:22:16
Message-ID: 20060307162216.57963.qmail@web53907.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> It seems risky, but you could probably get away with that as long
> as the database locale (LC_COLLATE/LC_CTYPE) is "C" ... which is really
> the only one that's safe with SQL_ASCII anyway ...

I actually created the cluster with:
test1:~# /usr/lib/postgresql/8.1/bin/initdb --pwprompt -D
/var/lib/postgresql/8.1/main/ --lc-collate=POSIX

test1:~# locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

Not sure if it's going to make a difference. Thanks

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Louis Gonzales 2006-03-07 20:29:37 postgresql-R
Previous Message Fabrice.Sznajderman 2006-03-07 16:09:48 Re: VACUUM Error?