Re: Passing server_encoding to the client is not future-proof

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Passing server_encoding to the client is not future-proof
Date: 2003-07-29 13:50:23
Message-ID: 21490.1059486623@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-07-29 13:53:56 Re: Passing server_encoding to the client is not future-proof
Previous Message vajjhala chakravarthi 2003-07-29 13:38:26 ACCESSING POST GRESQL DATABASE THRU MFCOBOL

Browse pgsql-jdbc by date

  From Date Subject
Next Message Rod Taylor 2003-07-29 13:53:56 Re: Passing server_encoding to the client is not future-proof
Previous Message Johann Uhrmann 2003-07-29 13:46:17 Asynchronous NOTIFY available?