Re: BUG #6246: character encoding for 64 bit - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #6246: character encoding for 64 bit
Date
Msg-id 4E9577B30200002500041EB4@gw.wicourts.gov
Whole thread Raw
In response to Re: BUG #6246: character encoding for 64 bit  (Susannah <cyclingrelf@gmail.com>)
Responses Re: BUG #6246: character encoding for 64 bit  (bushcraftrelf <cyclingrelf@gmail.com>)
List pgsql-bugs
Susannah <cyclingrelf@gmail.com> wrote:

> FATAL:  conversion between WIN1252 and LATIN1 is not supported

WIN1512 supports characters which are not supported by LATIN1.  If
you sent such characters to the database, what would you expect to
happen?

> I can connect through pgAdmin and create tables etc, just not with
> psql.

Perhaps pgAdmin detects the mismatch and sets the client-side
character set to the more limited LATIN1?  What does pgAdmin do if
you make such a connection and then try to store a character which
is not in the LATIN1 character set, like a euro character?

-Kevin

pgsql-bugs by date:

Previous
From: "Laurian Vostinar"
Date:
Subject: BUG #6253: JDBC driver: getIndexInfo() returns quotes around quoted column names
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #6252: After drop the default database 'postgres', I can not create a database by 'createdb.exe'