From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Craig Ringer <craig@2ndquadrant.com>,
 Andres Freund <andres@2ndquadrant.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: Changeset Extraction v7.0 (was logical changeset generation)
In-reply-to: 
 <CA+Tgmob=C2wfYKH9C1ke9-t6PrQrENFv8AtoncHCrg4f+wKtdg@mail.gmail.com>
References: <20140115002223.GA17204@awork2.anarazel.de>
 <CA+TgmoaWO2xU0LGQ_DFd0RaQM5ZRa8wB6u+-0UAdSrau1i0V=w@mail.gmail.com>
 <52D8A05C.5080504@2ndquadrant.com>
 <CA+Tgmob=C2wfYKH9C1ke9-t6PrQrENFv8AtoncHCrg4f+wKtdg@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
 message dated "Sat, 18 Jan 2014 08:31:55 -0500"
Date: Sat, 18 Jan 2014 12:04:07 -0500
Message-ID: <19833.1390064647@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Robert Haas <robertmhaas@gmail.com> writes:
> 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.

SHIFT_JIS is not and never will be allowed as a server encoding,
precisely because it has multi-byte characters of which some bytes could
be taken for ASCII.  The same is true of our other client-only encodings.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers