From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, 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-19 14:31:06 |
Message-ID: | 52DBE1AA.8060500@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/18/2014 02:31 PM, Robert Haas wrote:
> 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) */
while you have that file open: s/Winindows-932/Windows-932 maybe?
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2014-01-19 14:48:16 | Re: [bug fix] pg_ctl always uses the same event source |
Previous Message | Marko Tiikkaja | 2014-01-19 13:24:18 | Re: array_length(anyarray) |