Re: [HACKERS] [JDBC] JDBC driver reports a protocol error for a CVS HEAD server
On Tue, 24 Apr 2007, Ned T. Crigler wrote: The JDBC driver does not connect successfully to a CVS HEAD server (updated as of today) when using a database set to UTF8 encoding; enabling the debug messages in the driver shows that it is sending client_encoding=UNICODE in the startup packet, but the server is reporting client_encoding=UTF8 back to the driver, causing the driver to complain: Indeed, referring to -hackers as this is a recent backend change. The backend is reporting the database encoding as the client encoding. When a connection is created with a startup packet sending client_encoding = UNICODE the server responds with a ParameterStatus message of client_encoding = server encoding. So something has gone wrong here. It's not just a UNICODE/UTF-8 problem as I see the server responding with LATIN1 with a LATIN1 database. Kris Jurka ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] [JDBC] JDBC driver reports a protocol error for a CVS HEAD server
Kris Jurka [EMAIL PROTECTED] writes: On Tue, 24 Apr 2007, Ned T. Crigler wrote: The JDBC driver does not connect successfully to a CVS HEAD server (updated as of today) when using a database set to UTF8 encoding; Indeed, referring to -hackers as this is a recent backend change. The backend is reporting the database encoding as the client encoding. Confirmed here: psql has stopped obeying the PGCLIENTENCODING environment variable. Can't help suspecting that the recent GUC-parameter-rollback change broke it. (That has got to be one of the most snakebit projects we've had ... apparently the latest try needs reverted, again.) regards, tom lane ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
