> As far as I know, the node -1 error is caused by a slony version
> mismatch
> between nodes.

I have the same version of slony and postgres on both machines. Could
pgAdmin be appearing as a different slony version?

I've just done the same setup using slonik and not using pgAdmin at
all. I've managed to get this error everytime I've tried to add
tables into replication using pgAdmin, allthough I'll admit my
procedure of doing things was not consistant.

One thing I have noticed is that in the sl_listen table I now only
have 2 records. Previously I had 6, 4 of which pointed to node 99
which is the pgAdmin node.


The slonik scripts are very straight forward and a joy to use, so
I'll probably stick to these. I can also keep 1 slonik script with
everything I've done commented out in it so I can se what I've done
previously too.

Also whats the word on doing things from slonik scripts and then
doing bits from within pgAdmin? Recipie for disaster?


      __________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com