From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] invalid byte sequence ? |
Date: | 2006-08-25 15:07:03 |
Message-ID: | 200608251707.04128.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Am Donnerstag, 24. August 2006 00:52 schrieb Tom Lane:
> A possible solution therefore is to have psql or libpq drive the
> client_encoding off the client's locale environment instead of letting
> it default to equal the server_encoding.
I got started on this and just wanted to post an intermediate patch. I have
taken the logic from initdb and placed it into libpq and refined the API a
bit. At this point, there should be no behaviorial change. It remains to
make libpq use this stuff if PGCLIENTENCODING is not set. Unless someone
beats me, I'll figure that out later.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Attachment | Content-Type | Size |
---|---|---|
codeset-refactor.patch.gz | application/x-gzip | 3.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-08-25 15:30:40 | Re: [GENERAL] invalid byte sequence ? |
Previous Message | Randy How | 2006-08-25 14:51:30 | Re: FW: Serverlog 100GB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-25 15:11:54 | Re: Tricky bugs in concurrent index build |
Previous Message | Gregory Stark | 2006-08-25 15:06:50 | Re: Tricky bugs in concurrent index build |