From: | BladeOfLight16 <bladeoflight16(at)gmail(dot)com> |
---|---|
To: | Oliver <ofabelo(at)gmail(dot)com> |
Cc: | Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Change postgresql encoding |
Date: | 2015-02-08 20:50:16 |
Message-ID: | CA+=1U=UhYEHbDWBtsr9pp7y5mLyXEDH4UDVBqtdbUSxFwr9BPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Sun, Feb 8, 2015 at 2:20 PM, Oliver <ofabelo(at)gmail(dot)com> wrote:
> If I want change postgresql encoding, I have understood that I should
> reinstall postgresql (I do installation from rpm official binary files for
> red hat)
>
I can't answer your question about whether the encodings need to be the
same, but I'm pretty sure that's not true. CREATE DATABASE has options to
set the encoding for a database:
CREATE DATABASE korean WITH ENCODING 'EUC_KR' LC_COLLATE='ko_KR.euckr'
LC_CTYPE='ko_KR.euckr' TEMPLATE=template0;
(From http://www.postgresql.org/docs/9.4/static/multibyte.html)
To change the encoding of an existing PG database, you have to 1) dump it,
2) create a new, empty DB with the desired encoding, and 3) import the dump
into the new DB. So you can't really change it "on the fly," but it can be
done at creation time.
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver | 2015-02-09 07:52:05 | Re: [GENERAL] Change postgresql encoding |
Previous Message | Adrian Klaver | 2015-02-08 20:44:52 | Re: [GENERAL] Change postgresql encoding |
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2015-02-08 21:55:14 | Re: Partioning with overlapping and non overlapping constraints |
Previous Message | Adrian Klaver | 2015-02-08 20:44:52 | Re: [GENERAL] Change postgresql encoding |