Re: Changeset Extraction v7.0 (was logical changeset generation) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Changeset Extraction v7.0 (was logical changeset generation)
Date
Msg-id CA+Tgmob=C2wfYKH9C1ke9-t6PrQrENFv8AtoncHCrg4f+wKtdg@mail.gmail.com
Whole thread Raw
In response to Re: Changeset Extraction v7.0 (was logical changeset generation)  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Changeset Extraction v7.0 (was logical changeset generation)
Re: Changeset Extraction v7.0 (was logical changeset generation)
Re: Changeset Extraction v7.0 (was logical changeset generation)
List pgsql-hackers
On Thu, Jan 16, 2014 at 10:15 PM, Craig Ringer <craig@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Next
From: Robert Haas
Date:
Subject: Re: Changeset Extraction v7.0 (was logical changeset generation)