Some questions/hints:

1.) What versions of PG are you running? Some version of PG (I think it
was 8.2, but I'd had to check that) has become much more exact in
processing UTF-8. If you are replicating from an PG version that is
older than the version on the slaves this could be it.

2.) the client encoding is not much of an issue here, what is your
server encoding?

Andreas

Am Mittwoch, den 12.03.2008, 02:30 -0700 schrieb ajcity:
> Hi all,
>   I'm replicating a database that has 8 tables. 7 of them replicate fine on
> first replication but the last table (reports table) keeps giving this error
> whenever I try to replicate it:
> 2008-03-07 08:59:31 EST ERROR  remoteWorkerThread_1: copy from stdin on
> local node - PGRES_FATAL_ERROR ERROR:  invalid byte sequence for encoding
> "UTF8": 0x80
> 
> 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".
>  I have ran a SET CLIENT_ENCODING TO 'UTF-8' command on both the master and
> slave databases and I keep getting the same error. I have also dropped the
> table on the slave and recreated it with the exact schema of the master and
> still the same error.
>  I noticed that if I use pg_dump to extract the data on the reports table of
> the master and I insert it into the table on the slave, I don't get that
> error. Also, it seems to be giving the error on the last row of the table
> and the table is dynamically updated (on the average 5 times within the
> hour).
>   Does anyone have an idea as to what the problem could be?
> 
>      Victor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20080312/3be83f8a/attachment.pgp