| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Weiping <laser(at)qmail(dot)zhengmai(dot)net(dot)cn>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PGCLIENTENCODING behavior of current CVS source |
| Date: | 2004-11-16 15:57:17 |
| Message-ID: | 200411161657.17409.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am Dienstag, 16. November 2004 16:11 schrieb Tom Lane:
> This is a risk no matter what encoding is used in the client-side .po
> files; as long as it's different from the current client_encoding,
> there is a potential for mis-conversion and other problems. I don't
> see a simple solution.
Here's the news: Not only the server encoding and the server locale have to
match. The same is true on the client side. In particular, in order to
avoid errors from the PO files, your LC_CTYPE and your PGCLIENTENCODING need
to be compatible.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2004-11-16 16:08:48 | Re: 24x7x365 high-volume ops ideas |
| Previous Message | guenter strubinsky | 2004-11-16 15:57:06 | Re: PGCLIENTENCODING behavior of current CVS source |