The following bug has been logged online:

Bug reference: 2693
Logged by: Delight Chen
Email address: delight@nineder.com
PostgreSQL version: 8.1.4
Operating system: Red Hat Enterprise Linux ES release 4 (Nahant) Kernel
2.6.9-5.ELsmp on an x86_64
Description: Abut SQL ASCII through JDBC
Details:

I tried to install postgresql 8.1.4
Initdb with SQL_ASCII is work.
Create table is correct.
Insert Big5 text data correctly.
Try to view through /usr/local/pgsql/bin/psql and it's correct.
But when I try to query throught JDBC Driver, it always says "invalid byte
value for encoding"


And I tried another version 7.3.3 of postgresql.
Do all of thing above I metioned, and check it.
Finally I check data throught JDBC Driver, it's work correctly.


I think it's a bug for 8.1.4, so I report to you.



Here is the log of Version 8.1.4
LOG: duration: 1.700 ms statement: set datestyle to 'ISO'; select
version(), c
ase when pg_encoding_to_char(1) = 'SQL_ASCII' then 'UNKNOWN' else
getdatabaseenc
oding() end;
LOG: duration: 0.115 ms statement: set client_encoding = 'BIG5'; show
autocomm
it
ERROR: invalid byte value for encoding "SQL_ASCII": 0xa4


Here is the log of Version 7.3.3
LOG: query: set datestyle to 'ISO'; select version(), case when
pg_encoding_to_
char(1) = 'SQL_ASCII' then 'UNKNOWN' else getdatabaseencoding() end;
LOG: query: set client_encoding = 'BIG5'; show autocommit
LOG: query: select * from person_info where memo='大'

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Delight Chen wrote:
> Initdb with SQL_ASCII is work.

If you do that, most of the encoding stuff won't work correctly. Use
some other encoding.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match