Search Postgresql Archives

Re: client encoding that psql command sets

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Feb  7, 2014 at 09:12:10AM +0000, Albe Laurenz wrote:
> > Even when a LC_CTYPE environment variable was set up, the result did not change.
> > What do you think?
> 
> I think that the documentation contradicts the code.
> 
> In bin/psql/settings.h:
> 
> typedef struct _psqlSettings
> {
> [...]
>     bool        notty;          /* stdin or stdout is not a tty (as determined
>                                  * on startup) */
> [...]
> } PsqlSettings;
> 
> extern PsqlSettings pset;
> 
> In bin/psql/command.c and bin/psql/startup.c:
> 
>         keywords[6] = "client_encoding";
>         values[6] = (pset.notty || getenv("PGCLIENTENCODING")) ? NULL : "auto";
> 
> That matches your observations: client_encoding=auto is only
> used if both stdin and stdout are attached to a tty.
> 
> I suggest the attached documentation fix.

Patch applied and backpatched to 9.3.  Thanks.

-- 
  Bruce Momjian  <bruce@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux