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

From Rod Taylor
Subject Re: Passing server_encoding to the client is not future-proof
Date
Msg-id 1059486834.52827.7.camel@jester
Whole thread Raw
In response to Re: Passing server_encoding to the client is not future-proof  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 2003-07-29 at 09:50, Tom Lane wrote:
> 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.

It could still be useful for stored procedures (particularly Java ones)
which would have to deal with the encoding at the server.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Passing server_encoding to the client is not future-proof
Next
From: Carlos Guzman Alvarez
Date:
Subject: Re: Passing server_encoding to the client is not future-proof