Postgres Pro
Downloads
Home   >   mailing lists

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

From Susannah
Subject Re: BUG #6246: character encoding for 64 bit
Date
Msg-id loom.20111012T133820-528@post.gmane.org
Whole thread Raw
In response to BUG #6246: character encoding for 64 bit  ("Bo" <bo@budget123.dk>)
Responses Re: BUG #6246: character encoding for 64 bit  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-bugs
Tree view 
Bo <bo <at> budget123.dk> writes:

>
>
> The following bug has been logged online:
>
> Bug reference:      6246
> Logged by:          Bo
> Email address:      bo <at> budget123.dk
> PostgreSQL version: 9.1
> Operating system:   Windows server 2008
> Description:        character encoding for 64 bit
> Details:

>
> D:\>d:\PostgreSQL\9.1\bin\psql.exe -d demo_ -U postgres -c "comment on
> database demo_ is 'test'"
> Password for user postgres:
> psql: FATAL:  conversion between WIN1252 and LATIN1 is not supported
> *****************************
>
> Regards Bo TJ
>


I get a very similar error with both 64 bit and 32 bit postgres installations. I
have a table in LATIN1, but whenever I try to connect using psql, I get error
message:
postgres=# \c mydb
FATAL:  conversion between WIN1252 and LATIN1 is not supported
Previous connection kept

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

pgsql-bugs by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: *.sql contrib files contain unresolvable MODULE_PATHNAME
Next
From: "Can not create DB by 'createdb.exe' when DB 'postgres' is droped"
Date:
Subject: BUG #6252: After drop the default database 'postgres', I can not create a database by 'createdb.exe'