From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org, clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com |
Subject: | Re: Client encoding not the same as the db encoding |
Date: | 2012-02-29 14:57:58 |
Message-ID: | 201202290657.58910.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2012-02-29 15:02:05 | Easy way to corrupt a standby database |
Previous Message | Adam Bruss | 2012-02-29 14:54:44 | Re: accumulating handles problem on machine running postgresql |