| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Martel, Hong" <Hong(dot)Martel(at)saabsensis(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Language support of postgresql |
| Date: | 2017-05-02 18:20:32 |
| Message-ID: | 14080.1493749232@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Martel, Hong" <Hong(dot)Martel(at)saabsensis(dot)com> writes:
> As I understand, currently Postgres doesn$B!G(Bt 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?
Yes, and no. There's basically zero chance that we'll ever allow these
ecodings as server-side encodings, because they aren't strict ASCII
supersets (that is, not all bytes of a multibyte character are
individually distinguishable from an ASCII character). The amount of
work involved, and the ongoing hazard of security bugs that would ensue,
is just prohibitive.
We do however support them as client-side encodings with automatic
translation to and from Unicode on the server.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-05-02 18:41:20 | Re: Language support of postgresql |
| Previous Message | John R Pierce | 2017-05-02 16:40:13 | Re: Language support of postgresql |