Kevin Grittner wrote:
>
>
> WIN1512 supports characters which are not supported by LATIN1. If
> you sent such characters to the database, what would you expect to
> happen?
>
> -Kevin
>
Hi Kevin,
I forgot to mention a few things. One is that the problem only arises in
postgres 9.1 - I can
Surely the windows installation of psql ought to be set up to work with the
terminal already?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-6246-character-encoding-for-64-bit-tp4888531p4902052.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
I think I've figured it out - thanks all for your help. Craig Ringer appears
to be right.
>From documentation for psql 9.1 under Usage>Connecting to a database
"If at least one of standard input or standard output are a terminal, then
psql sets the client encoding to "auto", which will detect the
