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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 12:20:18
Message-ID: Pine.LNX.4.56.0307291419140.1370@krusty.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Tom Lane writes:

> Clients could probably still make use of server_encoding, though I'm
> unclear on what they'd use it for now, let alone then. ISTM
> client_encoding is the only setting the client need deal with directly.

Then why did we add a GUC variable "server_encoding" at all?

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-07-29 13:17:43 is 7.3.4 final?
Previous Message Merlin Moncure 2003-07-29 12:17:44 Re: an aggregate array function

Browse pgsql-jdbc by date

  From Date Subject
Next Message Ole Streicher 2003-07-29 12:43:44 Appending to a large object
Previous Message Ole Streicher 2003-07-29 10:04:05 Re: Another exception (Transaction level)