Re: SQL_ASCII vs. 7-bit ASCII encodings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SQL_ASCII vs. 7-bit ASCII encodings
Date
Msg-id 20236.1115961336@sss.pgh.pa.us
Whole thread Raw
In response to Re: SQL_ASCII vs. 7-bit ASCII encodings  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: SQL_ASCII vs. 7-bit ASCII encodings  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Re: SQL_ASCII vs. 7-bit ASCII encodings  (Oliver Jowett <oliver@opencloud.com>)
Re: SQL_ASCII vs. 7-bit ASCII encodings  (Alvaro Herrera <alvherre@surnet.cl>)
List pgsql-hackers
Oliver Jowett <oliver@opencloud.com> writes:
> Peter Eisentraut wrote:
>> That would cripple a system that many users are perfectly content with now.

> Well, I wasn't thinking of using a 7-bit encoding always, just as a
> replacement for the cases where we currently choose SQL_ASCII. Does that
> sound reasonable?

I agree with what (I think) Peter is saying: that would break things for
many people for whom the default works fine now.

We are currently seeing a whole lot of complaints due to the fact that
8.0 tends to default to Unicode encoding in environments where previous
versions defaulted to SQL-ASCII.  That says to me that a whole lot of
people were getting along just fine in SQL-ASCII, and therefore that
moving further away from that behavior is the wrong thing.  In
particular, there is not any single one of those complainants who would
be happier with a 7-bit-only default; if they were using 7-bit-only
data, they'd not have noticed a problem anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq lo_open errors when first action in connection
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: SQL_ASCII vs. 7-bit ASCII encodings