On 11-02-18 11:52 AM, Alessandro Sironi wrote:
> Hi, I'm new to Slony and I'm testing it for replicate some table between
> 2 Postgres DBs... today I had try the "MOVE SET" command executing this
> script on the slave:
>
> #!/usr/bin/slonik
> define CLUSTER clusterone;
> define PRIMARY 1;
> define SLAVE 10;
>
> cluster name = @CLUSTER;
> node @PRIMARY admin conninfo = 'dbname=NameDB host=IPMaster
> user=test-slony';
> node @SLAVE admin conninfo = 'dbname=NameDB host=IPSlave user=test-slony';
>
> LOCK SET(ID=1, ORIGIN=@PRIMARY);
> MOVE SET(ID=1, OLD ORIGIN=@PRIMARY, NEW ORIGIN=@SLAVE);
>
> ...after this I execute the same script (with @PRIMARY and @SLAVE
> inverted)on the PRIMARY node (to get back to the previous situation) but
> I obtain thefollowing error:
>
> ./script4.sk:10: PGRES_FATAL_ERROR select "_cname".lockSet(1); select
> "_cname".getMaxXid(); - ERROR: Slony-I: set 1 does not originate on
> local node

It sounds like the move set didn't get picked up by the other node.

If you do

select * FROM _cname.sl_set;

on both nodes, do they disagree about which node is the origin of the set?

Are your slons running? Reporting any errors?






>
> ...now @SLAVE and @PRIMARY node result both as subscriber to the set
> with ID 1 and I can't delete/drop the set.
> What did I do wrong? There is a way to get all back to normal?
>



>
> Thanks in advance.
> Alex
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general