From: <cbbrowne at ca.afilias.info>

> The problem appears to be a mismatch of slon versions.

?? scratches head ??

psql avbrief -h k -c "select \"_T1\".slonyversion()"
 slonyversion
--------------
 1.1.0
(1 row)

psql avbrief -h j -c "select \"_T1\".slonyversion()"
 slonyversion
--------------
 1.1.0
(1 row)

On k:
slon -h
2005-05-01 17:32:48 UTC CONFIG main: slon version 1.1.0 starting up

On j:
slon -h
2005-05-01 17:33:04 UTC CONFIG main: slon version 1.1.0 starting up

I've run update functions on both. I've installed both via (homespun) RPMs 
with file lists as follows:

/usr/bin/slon
/usr/bin/slonik
/usr/lib/pgsql/slony1_funcs.so
/usr/lib/pgsql/xxid.so
/usr/share/doc/slony1-1.1.0.beta1
/usr/share/doc/slony1-1.1.0.beta1/COPYRIGHT
/usr/share/pgsql/slon.conf-sample
/usr/share/pgsql/slony1_base.sql
/usr/share/pgsql/slony1_base.v73.sql
/usr/share/pgsql/slony1_base.v74.sql
/usr/share/pgsql/slony1_funcs.sql
/usr/share/pgsql/slony1_funcs.v73.sql
/usr/share/pgsql/slony1_funcs.v74.sql
/usr/share/pgsql/xxid.v73.sql
/usr/share/pgsql/xxid.v74.sql

Every file is identical in date and size between the pair.  The source used 
was slony1-1.1.0.beta1.tar.gz (611756 bytes)

Is there anything that might possibly be hanging around from previous 
versions? (I had 1.05 installed for a while, I think).

> The "latest" slon knows about the ACCEPT_SET event (which is a new event
> created to prevent data loss when a MOVE_SET takes place; a node holds off
> on applying changes until it has gotten both...)
>
> But evidently one of the slons you are running doesn't include ACCEPT_SET
> in its set of events.

Any way of testing what events it will accept?

Regards

Julian