Re: current breakage with PGCLIENTENCODING - Mailing list pgsql-hackers

From Tom Lane
Subject Re: current breakage with PGCLIENTENCODING
Date
Msg-id 24710.1051456479@sss.pgh.pa.us
Whole thread Raw
In response to Re: current breakage with PGCLIENTENCODING  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> I guess that's because your database encoding is SQL_ASCII. Could you
> try with an EUC_JP encoded database?

I get the same results with UNICODE or EUC_JP databases:
pg_client_encoding() reports SJIS as expected.

It does look like something's broken though, because some of the
src/test/mb tests fail:

$ sh mbregress.sh
dropdb: database removal failed: ERROR:  DROP DATABASE: database "unitest" does
not exist
CREATE DATABASE
euc_jp ..  ok
sjis ..  failed
euc_kr ..  ok
euc_cn ..  ok
euc_tw ..  ok
big5 ..  failed
unicode ..  ok
mule_internal ..  ok
$

The full diffs are attached --- do they make any sense to you?  At least
some of the changes are intentional: the parser error position is now
counted in characters not bytes.

            regards, tom lane


Attachment

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: current breakage with PGCLIENTENCODING
Next
From: Tom Lane
Date:
Subject: Re: current breakage with PGCLIENTENCODING