Re: Client encoding not the same as the db encoding - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Client encoding not the same as the db encoding
Date
Msg-id 201202290657.58910.adrian.klaver@gmail.com
Whole thread Raw
In response to Client encoding not the same as the db encoding  (Clodoaldo Neto <clodoaldo.pinto.neto@gmail.com>)
Responses Re: Client encoding not the same as the db encoding  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wednesday, February 29, 2012 6:47:21 am Clodoaldo Neto wrote:
> In 9.1.3 the client encoding is not defaulting to the db encoding:
>
> postgresql.conf:
>
> #client_encoding = sql_ascii
>
> => show server_encoding;
>  server_encoding
> -----------------
>  SQL_ASCII
>
> => show client_encoding;
>  client_encoding
> -----------------
>  UTF8
>
> In 9.0 the client encoding defaults to the db encoding:
>
> postgresql.conf:
>
> #client_encoding = sql_ascii
>
> => show client_encoding;
>  client_encoding
> -----------------
>  SQL_ASCII
>
> => show server_encoding;
>  server_encoding
> -----------------
>  SQL_ASCII
>
> What am i missing? Regards, Clodoaldo

My guess this:
http://www.postgresql.org/docs/9.1/interactive/release-9-1.html
"E.4.3.10.1. libpq

Add a libpq connection option client_encoding which behaves like
he PGCLIENTENCODING environment variable (Heikki Linnakangas)
The value auto sets the client encoding based on the operating
system locale.
"

Which leads to this:
http://www.postgresql.org/docs/9.1/interactive/libpq-connect.html#LIBPQ-CONNECT-CLIENT-ENCODING

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Adam Bruss
Date:
Subject: Re: accumulating handles problem on machine running postgresql
Next
From: Chris Travers
Date:
Subject: Easy way to corrupt a standby database