| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changeset Extraction v7.0 (was logical changeset generation) |
| Date: | 2014-01-18 13:31:55 |
| Message-ID: | CA+Tgmob=C2wfYKH9C1ke9-t6PrQrENFv8AtoncHCrg4f+wKtdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 16, 2014 at 10:15 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Anybody who actually uses SHIFT_JIS as an operational encoding, rather
> than as an input/output encoding, is into pain and suffering. Personally
> I'd be quite happy to see it supported as client_encoding, but forbidden
> as a server-side encoding. That's not the case right now - so since we
> support it, we'd better guard against its quirks.
I think that *is* the case right now. pg_wchar.h sayeth:
/* followings are for client encoding only */
PG_SJIS, /* Shift JIS
(Winindows-932) */
PG_BIG5, /* Big5 (Windows-950) */
PG_GBK, /* GBK (Windows-936) */
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-01-18 13:35:47 | Re: Changeset Extraction v7.0 (was logical changeset generation) |
| Previous Message | Robert Haas | 2014-01-18 13:28:14 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |