Re: Language support of postgresql

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Language support of postgresql
Date: 2017-05-02 16:40:13
Message-ID: d47a4f2f-600c-5b7c-feed-6a33da71083d@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 4/28/2017 7:45 AM, Martel, Hong wrote:
>
> As I understand, currently Postgres doesn’t support Chinese encoding
> GBK and BIG5 on both server and client side, only UNICODE. Is it
> true? Are there any plans for postgresql team to implement GBK and
> BIG5 encoding anytime soon?
>
> Are there any alternative solutions for this besides switching our
> database to Oracle or others that support the encodings? One of our
> customers insists that we need to support all three encoding (BIG5,
> GB2312安and UNICODE). We would love to stick to Postgres if there is
> any alternative way to solve the problem without incurring big cost.
>

I thought Postgres supported client_encodings of BIG5, GB18030, and GBK,
all of which can be stored in the server using either UTF8 or
MULE_INTERNAL (MultiLingual EMACS) encodings for internal storage ?

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-05-02 18:20:32 Re: Language support of postgresql
Previous Message Alvaro Aguayo Garcia-Rada 2017-05-02 16:18:22 Re: BDR replication and table triggers