From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: current breakage with PGCLIENTENCODING |
Date: | 2003-04-27 15:14:39 |
Message-ID: | 24710.1051456479@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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 | Content-Type | Size |
---|---|---|
regression.diffs | application/octet-stream | 11.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-04-27 16:26:25 | Re: current breakage with PGCLIENTENCODING |
Previous Message | Tatsuo Ishii | 2003-04-27 10:08:07 | Re: current breakage with PGCLIENTENCODING |