| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] invalid byte sequence ? |
| Date: | 2006-08-25 18:43:34 |
| Message-ID: | 4361.1156531414@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> And as a counter-example: pg_dump should absolutly not use the client
> locale, it should always dump as the same encoding as the server...
Sure, but pg_dump should set that explicitly. I'm prepared to believe
that looking at the locale is sane for all normal clients.
It might be worth providing a way to set the client_encoding through a
PQconnectdb connection-string keyword, just in case the override-via-
PGCLIENTENCODING dodge doesn't suit someone. The priority order
would presumably be connection string, then PGCLIENTENCODING, then
locale.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Bertini | 2006-08-25 18:48:43 | Re: hint unique result fro union |
| Previous Message | Martijn van Oosterhout | 2006-08-25 18:37:11 | Re: [GENERAL] invalid byte sequence ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-08-25 18:53:59 | Re: [GENERAL] invalid byte sequence ? |
| Previous Message | Martijn van Oosterhout | 2006-08-25 18:37:11 | Re: [GENERAL] invalid byte sequence ? |