Changing locale/charset

Started by Martin Mooreabout 8 years ago3 messagesgeneral
Jump to latest
#1Martin Moore
martin.moore@avbrief.com

I created a 10.1 cluster on Debian using UTF8.
I’d like to convert it to LATIN1, but am having various issues. So, it’s probably easiest to start again (I have a dump of the DB).

To ensure I get it right, what is the correct way to create a cluster with LATIN1 encoding, how to remove the existing cluster and how to ensure I have the right settings for LOCALE etc. in the OS?

Cheers.

#2Peter Eisentraut
peter_e@gmx.net
In reply to: Martin Moore (#1)
Re: Changing locale/charset

On 1/22/18 16:18, Martin Moore wrote:

I created a 10.1 cluster on Debian using UTF8.
I’d like to convert it to LATIN1, but am having various issues. So, it’s probably easiest to start again (I have a dump of the DB).

To ensure I get it right, what is the correct way to create a cluster with LATIN1 encoding, how to remove the existing cluster and how to ensure I have the right settings for LOCALE etc. in the OS?

pg_lsclusters
pg_dropcluster VERSION NAME
pg_createcluster VERSION NAME --locale=xx_XX

where xx_XX is chosen by you. You previous cluster probably had a
locale of xx_XX.utf8, so it had the UTF8 encoding.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

#3Adrian Klaver
adrian.klaver@aklaver.com
In reply to: Martin Moore (#1)
Re: Changing locale/charset

On 01/22/2018 01:18 PM, Martin Moore wrote:

I created a 10.1 cluster on Debian using UTF8.
I’d like to convert it to LATIN1, but am having various issues. So, it’s probably easiest to start again (I have a dump of the DB).

To ensure I get it right, what is the correct way to create a cluster with LATIN1 encoding, how to remove the existing cluster and how to ensure I have the right settings for LOCALE etc. in the OS?

Assuming you are using the Debian pg_ctlcluster command see 'Changing
Debian default installation' in below:

https://wiki.debian.org/PostgreSql

Cheers.

--
Adrian Klaver
adrian.klaver@aklaver.com