Re: New database: SQL_ASCII vs UTF-8 trade-offs - Mailing list pgsql-admin

From Tom Lane
Subject Re: New database: SQL_ASCII vs UTF-8 trade-offs
Date
Msg-id 19681.1141747646@sss.pgh.pa.us
Whole thread Raw
In response to Re: New database: SQL_ASCII vs UTF-8 trade-offs  (ow <oneway_111@yahoo.com>)
Responses Re: New database: SQL_ASCII vs UTF-8 trade-offs  (ow <oneway_111@yahoo.com>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: ow
Date:
Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs
Next
From: Fabrice.Sznajderman@devoteam.com
Date:
Subject: Re: VACUUM Error?