From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: character encoding of the postgres database |
Date: | 2017-05-10 16:54:11 |
Message-ID: | 18585ecf-26c4-c4d6-d65a-988be0f144af@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/10/2017 08:48 AM, Sandeep Gupta wrote:
> Currently, the postgres database by has SQL_ASCII encoding.
>
> psql -p 5771 postgres -l
> List of databases
> Name | Owner | Encoding | Collate | Ctype | Access privileges
> -----------+---------+-----------+---------+-------+---------------------
> postgres | sandeep | SQL_ASCII | C | C |
> template0 | sandeep | SQL_ASCII | C | C | =c/sandeep +
> | | | | | sandeep=CTc/sandeep
> template1 | sandeep | SQL_ASCII | C | C | =c/sandeep +
> | | | | | sandeep=CTc/sandeep
> (3 rows)
>
> Is it possible to start the postgres database with UTF-8 encoding, instead
> of modifying it later.
See Peter's post, just remember that SQL_ASCII is essentially no
encoding so be prepared for issues. I would test before doing this on
live data.
>
> Thanks
> sandeep
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-05-10 16:55:02 | Re: Upgrading postgresql minor version |
Previous Message | David G. Johnston | 2017-05-10 16:34:45 | Re: Upgrading postgresql minor version |