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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ow <oneway_111(at)yahoo(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs
Date: 2006-03-07 16:07:26
Message-ID: 19681.1141747646@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

ow <oneway_111(at)yahoo(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Fabrice.Sznajderman 2006-03-07 16:09:48 Re: VACUUM Error?
Previous Message ow 2006-03-07 15:48:59 Re: New database: SQL_ASCII vs UTF-8 trade-offs