| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Determining client_encoding from client locale |
| Date: | 2009-06-17 12:52:20 |
| Message-ID: | 4A38E704.40008@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
>
> client_encoding defaults to server_encoding, which is correct in the
> typical environment where the client and the server have identical
> locale settings, which I believe is why we don't see more confused
> users on mailing lists. However, a partner of ours was recently bitten
> by this. That was on Windows; I'm not 100% sure if LC_CTYPE is set
> correctly there by default, but this seems like a good idea nevertheless.
>
IIRC Windows locales are not set via the environment. We've had to do
some special hackery in a few placed to deal with that.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-06-17 13:36:59 | Re: Determining client_encoding from client locale |
| Previous Message | Stefan Kaltenbrunner | 2009-06-17 12:41:56 | Re: [PATCH] backend: compare word-at-a-time in bcTruelen |