Re: BUG #5801: characters not encoded properly for column names

Le jeudi 23 d=C3=A9cembre 2010 18:21:55, John R Pierce a =C3=A9crit :
> On 12/23/10 2:34 AM, Marc Cousin wrote:
> > No, from a Linux psql client (inside a kde konsole). You can setup any
> > charset in it. I have exactly the same behaviour with psql under windows
> > anyway, with a chcp 1252 in the cmd console. It's not a console charset
> > problem, I've tripled checked that :)
> >=20
> > And anyway, this character shouldn't get into the database as UTF8, as =
it
> > is 1252 (hence the error message).
>=20
> does client_encoding affect names ?  (I'm asking because I have no idea).
Yes (for the Linux server, for Windows it fails).
I have exactly the same problem if I test with LATIN9 (except that the utf8=
=20
error message has a different value for the bad character).

>=20
> what encodings are the database clusters on the two platforms?

Oh. Both are UTF-8.