| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Andreas <maps(dot)on(at)gmx(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: invalid byte sequence ? |
| Date: | 2006-08-24 14:01:05 |
| Message-ID: | 3942.1156428065@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Martijn van Oosterhout wrote:
>> It seems to me that setting the client encoding based on the
>> client-locale is the *only* sensible way of doing it.
> Yes please.
> FWIW I'm not sure if it really belongs in libpq, or it must be rather in
> psql (and thus in every client).
libpq is what implements PGCLIENTENCODING, so I'd say that's where any
change in the default has to be handled. Presumably we'd still allow
PGCLIENTENCODING to override the locale?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajarshi Guha | 2006-08-24 14:01:34 | getting around 'out of memory' errors |
| Previous Message | Michael Fuhr | 2006-08-24 13:45:49 | Re: Saving a jpg into Postgresql table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2006-08-24 14:49:00 | Re: Replication |
| Previous Message | Tom Lane | 2006-08-24 13:58:10 | Re: Autovacuum on by default? |