Re: Reg:CHARSET_COVERSION_LATIN_TO_UTF8 - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Reg:CHARSET_COVERSION_LATIN_TO_UTF8
Date
Msg-id CABUevEyOuQ7K3uN23M4VBF1KnJAdAWu69mGb0qGeXGGC1JcKSw@mail.gmail.com
Whole thread Raw
In response to Reg:CHARSET_COVERSION_LATIN_TO_UTF8  (nandha kumar <bnandhakumardba@gmail.com>)
List pgsql-general


On Mon, Sep 14, 2020 at 7:17 AM nandha kumar <bnandhakumardba@gmail.com> wrote:
Hi Team,
I have the postgresql database with 11.4 Version in AWS RDS. Some of the columns have lattin collate format. I need to migrate the database to Azure postgresql and need to convert UTF8 column format.

How to find which columns are in Latin format. How to convert the data and columns to UTF8.


PostgreSQL doesn't have different encoding (aka charset) on different columns, only on databases. Latin1 and UTF8 are encodings. Columns can have different collations, but not different encodings.

You can check your database encodings with \l in psql. All tables and columns in one database will have the same encoding as the one listed for the database. If you are using pg_dump to do the migration, you can use the -E parameter to make sure the data is dumped in UTF8 format, reload that, and all should be taken care of.

--

pgsql-general by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Why SELECT COUNT(*) takes so long?
Next
From: luis.roberto@siscobra.com.br
Date:
Subject: Effective IO Concurrency