Horton

Re: Unicode UTF-8 table formatting for psql text output

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: "Brad T. Sliger" <brad@sliger.org>, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>, Selena Deckelmann <selenamarie@gmail.com>, Roger Leigh <rleigh@codelibre.net>, Alvaro Herrera <alvherre@commandprompt.com>, Roger Leigh <rleigh@debian.org>
Date: 2009-09-29T20:28:57Z
Lists: pgsql-hackers 
Peter Eisentraut <peter_e@gmx.net> writes:
> On Tue, 2009-09-29 at 12:01 -0400, Tom Lane wrote:
>> The bigger question is exactly how we expect this stuff to interact with
>> pg_regress' --no-locale switch.  We already do clear all these variables
>> when --no-locale is specified.  I am wondering just what --locale is
>> supposed to do, and whether selectively lobotomizing the LC stuff has
>> any real use at all.

> We should do the LANG or LC_CTYPE thing only on the client,
> unconditionally.  The --no-locale/--locale options should primarily
> determine what the temporary server uses.

Well, that seems fairly reasonable, but it's going to require some
refactoring of pg_regress.  The initialize_environment function
determines what happens in both the client and the temp server.

			regards, tom lane