Re: BUG #5801: characters not encoded properly for column names - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #5801: characters not encoded properly for column names
Date
Msg-id 4D138533.2080105@hogranch.com
Whole thread Raw
In response to Re: BUG #5801: characters not encoded properly for column names  (Marc Cousin <cousinmarc@gmail.com>)
Responses Re: BUG #5801: characters not encoded properly for column names  (Marc Cousin <cousinmarc@gmail.com>)
List pgsql-bugs
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 :)
>
> And anyway, this character shouldn't get into the database as UTF8, as it is
> 1252 (hence the error message).

does client_encoding affect names ?  (I'm asking because I have no idea).

what encodings are the database clusters on the two platforms?

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Issue while using PostgreSql 8.4.
Next
From: Marc Cousin
Date:
Subject: Re: BUG #5801: characters not encoded properly for column names