Postgres Pro
Downloads
Home   >   mailing lists

Re: Passing server_encoding to the client is not future-proof - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Passing server_encoding to the client is not future-proof
Date
Msg-id 21490.1059486623@sss.pgh.pa.us
Whole thread Raw
In response to Re: Passing server_encoding to the client is not future-proof  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Passing server_encoding to the client is not future-proof  (Rod Taylor <rbt@rbt.ca>)
Re: Passing server_encoding to the client is not future-proof  (Carlos Guzman Alvarez <carlosga@telefonica.net>)
Re: Passing server_encoding to the client is not future-proof  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tree view 
Peter Eisentraut <peter_e@gmx.net> writes:
> Then why did we add a GUC variable "server_encoding" at all?

The JDBC guys wanted to know it.  Why is not clear to me, but I figured
it was easy enough to make them happy.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: is 7.3.4 final?
Next
From: Rod Taylor
Date:
Subject: Re: Passing server_encoding to the client is not future-proof