Jeff Davis wrote:
> On Wed, 2008-06-11 at 14:01 -0400, Geoffrey wrote:
>> remoteWorkerThread_1: copy from stdin on local node - PGRES_FATAL_ERROR 
>> ERROR:  invalid byte sequence for encoding "UTF8": 0xfa
>> HINT:  This error can also happen if the byte sequence does not match 
>> the encoding expected by the server, which is controlled by 
>> "client_encoding".
>> CONTEXT:  COPY avlds, line 339294
>>
>> Is this a complaint because Slony expects one type of encoding and 
>> Postgresql is using a different one?  Or is it because of difference 
>> encoding between the two nodes?  As far as I can see, the encoding is 
>> the same on both nodes.
> 
> If the encoding is the same everywhere, and you are using PostgreSQL
> 8.2, it's likely that you got an invalid byte sequence in a text field
> by using backslash-escapes.
> 
> Once that happens, COPY will no longer work correctly. In fact, a
> pg_dump might not be able to be restored.
> 
> Slony relies on COPY working correctly, so it's failing for that reason.
> 
> Try sanitizing your data to be valid UTF-8 or only using the C locale
> (SQL_ASCII encoding).

I think I'm on to something here.  The encoding is in fact different on 
the two nodes.  I'm going to correct that issue and retry my replication.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin