Message-ID: <4AF0FAF9.8080306@obviously.com>
Date: Tue, 03 Nov 2009 19:54:33 -0800
From: Bryce Nesbitt <bryce2@obviously.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
CC: Craig Ringer <craig@postnewspapers.com.au>
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
References: <4AF0D531.5080309@obviously.com>
	<4AF0E70F.1030201@postnewspapers.com.au>
	<4AF0F6A7.7070505@obviously.com>
	<4AF0F949.3060807@postnewspapers.com.au>
In-Reply-To: <4AF0F949.3060807@postnewspapers.com.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Craig Ringer wrote:
> Yes - but you are *not* presenting a Latin-1 character. You're
> presenting four Latin-1 characters:
>
>   '\', '3', '7', '5'
Well, then I have a different question.  If I can view a bytea column as so:

 > select object from context_objects where context_key=100041;
           object
-----------------------------
 \005\007\021\007Article\003
(1 row)

How can I modify the data and put it back into the column?

I'm trying to track down while a ten year old system no longer works 
after a Perl DBI upgrade.  Something is munging high LATIN1.  The DB 
itself is UTF-8, client_encoding is set to LATIN1.  We expect LATIN1 in, 
same stuff out.  But right now that is what I'm debugging.