From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: regression test client encoding |
Date: | 2011-04-15 21:11:41 |
Message-ID: | 1217.1302901901@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On Fri, 2011-04-15 at 16:09 -0400, Tom Lane wrote:
>> That doesn't seem like a particularly good idea in view of the recent
>> changes in psql to try to intuit a default encoding from its locale
>> environment. If I say --encoding in the command line, that means I want
>> that encoding, not an environment-dependent one.
> Actually, in light of that we might want to override PGCLIENTENCODING to
> SQL_ASCII, so we get back the results in ASCII (assuming an all-ASCII
> test), instead of whatever the client encoding might say, which might
> not be an ASCII superset.
Well, if you set client_encoding to that, what you will get is no
conversion, which is exactly the same result as what you'll get from
setting it the same as server_encoding, which is the current behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-04-15 21:33:38 | Re: Single client performance on trivial SELECTs |
Previous Message | Peter Eisentraut | 2011-04-15 20:46:48 | Re: regression test client encoding |