From: Tom Lane <tgl@sss.pgh.pa.us>
To: ow <oneway_111@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs
Date: Tue, 07 Mar 2006 11:07:26 -0500
Message-ID: <19681.1141747646@sss.pgh.pa.us> (raw)
In-Reply-To: <20060307154859.55607.qmail@web53903.mail.yahoo.com>
References: <20060307154859.55607.qmail@web53903.mail.yahoo.com>
ow <oneway_111@yahoo.com> writes:
> I see... If *ALL* data is in ASCII, is it possible to just update
> "pg_database.encoding" to UTF-8 or will I need to recreate the db?
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 ... note that
already-started backends will probably fail to notice such a change.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, oneway_111@yahoo.com
Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs
In-Reply-To: <19681.1141747646@sss.pgh.pa.us>
References: <20060307154859.55607.qmail@web53903.mail.yahoo.com> <19681.1141747646@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox