On Friday, November 25, 2011 1:19:29 am Condor wrote:
> early postgresql versions (< 9.1) did not show this error message:
> FATAL conversion between LATIN1 and WIN1251 is not supported
> and connect to db. I access server over the network and every time when
> I try to login because I work on latin1 I should export
> for example. With few terminals on few different databases that is
> pretty disgustingly.
> Any way how I can avoid it ?
Did the 9.1 database get created with a different character set then on previous
See here for automatic conversions:
Going back to 8.3 at least I do not see that it has changed.
Going to release notes:
Have psql set the client encoding from the operating system locale by default
This only happens if the PGCLIENTENCODING environment variable is not set.
This led me to:
Sets the client-side encoding (character set). The default is to use the
database encoding. The character sets supported by the PostgreSQL server are
described in Section 22.3.1.
In response to
pgsql-general by date
|Next:||From: Gaëtan Allart||Date: 2011-11-25 22:47:32|
|Subject: Re: General performance/load issue|
|Previous:||From: Adrian Klaver||Date: 2011-11-25 22:29:05|
|Subject: Re: .dmp files in postgresql|