| From: | Marc Cousin <cousinmarc(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5801: characters not encoded properly for column names |
| Date: | 2010-12-23 17:29:49 |
| Message-ID: | 201012231829.49400.cousinmarc@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Le jeudi 23 décembre 2010 18:21:55, John R Pierce a écrit :
> 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).
Yes (for the Linux server, for Windows it fails).
I have exactly the same problem if I test with LATIN9 (except that the utf8
error message has a different value for the bad character).
>
> what encodings are the database clusters on the two platforms?
Oh. Both are UTF-8.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trimurthulu Bandaru | 2010-12-24 11:57:12 | insert statement going into infinite loop |
| Previous Message | John R Pierce | 2010-12-23 17:21:55 | Re: BUG #5801: characters not encoded properly for column names |