Re: Changing DB Encodings - Mailing list pgsql-general

From Tom Lane
Subject Re: Changing DB Encodings
Date
Msg-id 13823.1183848051@sss.pgh.pa.us
Whole thread Raw
In response to Changing DB Encodings  (Naz Gassiep <naz@mira.net>)
Responses Re: Changing DB Encodings  (Naz Gassiep <naz@mira.net>)
List pgsql-general
Naz Gassiep <naz@mira.net> writes:
> Why have I been told that I need to do a re initdb to change the char
> encoding? The man says i can just     createdb foodb -E utf8    so why
> would i need to dump/initdb/create/restore? cant i just dump/create/restore?

Are you clear on the difference between encoding and locale?

You can make new databases with whatever encoding you say, but the
server's lc_collate and lc_ctype are frozen at initdb, and it will
not work well to select an encoding that is incompatible with the
locale setting.  In practice this means that you can only use multiple
database encodings when you initdb'd in "C" locale; all other locale
settings imply a particular encoding.

Yes, this is pretty annoying.  No, it's not easy to fix.

            regards, tom lane

pgsql-general by date:

Previous
From: Naz Gassiep
Date:
Subject: Changing DB Encodings
Next
From: Raymond O'Donnell
Date:
Subject: Re: catalog location