Skip site navigation (1) Skip section navigation (2)

Re: Client encoding not the same as the db encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: 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 15:50:33
Message-ID: 1232.1330530633@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> 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:
>> 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.
> "

No, probably more this (under "psql")

	* Have psql set the client encoding from the operating system locale by default (Heikki Linnakangas)

	This only happens if the PGCLIENTENCODING environment variable is not set.

I think the idea was to try to match your terminal window's encoding
automatically.

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: David GrecoDate: 2012-02-29 15:51:56
Subject: Calling Functions With OUT paramaters
Previous:From: Chris TraversDate: 2012-02-29 15:02:05
Subject: Easy way to corrupt a standby database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group