Hello,

2010/4/30 Jan Wieck <JanWieck at yahoo.com>
>
> > FWIW, I am hitting this issue, too. This does not happen in 1.2.X.
> >
> > Both machines are very identical (using the same postgresql.conf), and
> > they are running 8.4.3 with RPM installations. FWIW I had this issue in
> > 2.0.3RC3, too.
> >
> > I had to use 1.2.21 yesterday night on a new installation.
>
> Is anyone able to give me one single text datum that will cause this?
>

I am running Slony 2.0.3 against Postgres 8.4.3  on a CentOS 5.5
machine, and am running into the same issue. This is a development
machine, and the two slony / database instances are both on the same
machine, so library incompatibilities/etc are exluded.
The PostgreSQL logfile says something like this:
--
LOG:  statement: begin transaction; set transaction isolation level
serializable;
LOG:  statement: select SSY.ssy_setid, SSY.ssy_seqno,
"pg_catalog".txid_snapshot_xmax(SSY.ssy_snapshot),
SSY.ssy_snapshot,     SSY.ssy_action_list from "_tsukku".sl_setsync
SSY where SSY.ssy_seqno < '5000000742'     and SSY.ssy_setid in
(1,2,3);
LOG:  statement: select T.tab_id, T.tab_set,
"_tsukku".slon_quote_brute(PGN.nspname) || '.' ||
"_tsukku".slon_quote_brute (PGC.relname) as tab_fqname from
"_tsukku".sl_table T, "pg_catalog".pg_class PGC,
"pg_catalog".pg_namespace PGN where T.tab_set = 1     and PGC.oid =
T.tab_reloid     and PGC.relnamespace = PGN.oid;
LOG:  statement: select T.tab_id, T.tab_set,
"_tsukku".slon_quote_brute(PGN.nspname) || '.' ||
"_tsukku".slon_quote_brute (PGC.relname) as tab_fqname from
"_tsukku".sl_table T,     "pg_catalog".pg_class PGC,
"pg_catalog".pg_namespace PGN where T.tab_set = 2     and PGC.oid =
T.tab_reloid     and PGC.relnamespace = PGN.oid;
LOG:  statement: select T.tab_id, T.tab_set,
"_tsukku".slon_quote_brute(PGN.nspname) || '.' ||
"_tsukku".slon_quote_brute (PGC.relname) as tab_fqname from
"_tsukku".sl_table T,     "pg_catalog".pg_class PGC,
"pg_catalog".pg_namespace PGN where T.tab_set = 3     and PGC.oid =
T.tab_reloid     and PGC.relnamespace = PGN.oid;
LOG:  statement: select last_value from "_tsukku".sl_log_status
ERROR:  invalid byte sequence for encoding "UTF8": 0xb0
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".
ERROR:  invalid byte sequence for encoding "UTF8": 0xb0
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".
LOG:  statement: rollback transaction
--

I will try to find out what log entry is causing the trouble.