From: | Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: character encoding of the postgres database |
Date: | 2017-05-10 18:09:48 |
Message-ID: | CAAywg7u2eGkP50UFGR17UtAygGDomPDxdb8WZrfYeM-kPE581w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you.
On Wed, May 10, 2017 at 12:54 PM, Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com> wrote:
> 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 | Hu, Patricia | 2017-05-10 18:31:43 | Re: relation create time |
Previous Message | Rajesh Mallah | 2017-05-10 17:39:56 | Re: logging of application level user in audit trigger |