Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] invalid byte sequence ?

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: (view raw or whole thread)
Lists: pgsql-generalpgsql-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

Attachment: codeset-refactor.patch.gz
Description: application/x-gzip (3.0 KB)

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-08-25 15:11:54
Subject: Re: Tricky bugs in concurrent index build
Previous:From: Gregory StarkDate: 2006-08-25 15:06:50
Subject: Re: Tricky bugs in concurrent index build

pgsql-general by date

Next:From: Martijn van OosterhoutDate: 2006-08-25 15:30:40
Subject: Re: [GENERAL] invalid byte sequence ?
Previous:From: Randy HowDate: 2006-08-25 14:51:30
Subject: Re: FW: Serverlog 100GB

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group