When I do a MOVE SET, I am seeing the "forward" attribute getting set to
TRUE on the subscription. I have two nodes, an active and a standby,
running slony 1.0.2. Is this correct behavior?
 
In some situations when I try to then do a MOVE SET back (i.e., a
"fail-back"), I am seeing the MOVE SET hang. I'm wondering if this is
related to the forward being set to TRUE or not. Here is my move set
command (this particular command did not hang - the format is always the
same because it's generated):
 
CLUSTER NAME = tzreplic;
 
NODE 1 ADMIN CONNINFO = 'host=192.168.111.62 port=24005 dbname=policy
user=tazz:dbmgr password=tazz:dbmgr';
NODE 2 ADMIN CONNINFO = 'host=192.168.111.65 port=24005 dbname=policy
user=tazz:dbmgr password=tazz:dbmgr';

LOCK SET (ID = 1, ORIGIN = 1);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = 2);
MOVE SET (ID = 1, OLD ORIGIN = 1, NEW ORIGIN = 2);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = 2);

I assume I'm missing something in my syntax somewhere.
 
Any clues appreciated. Thanks.

- DAP
------------------------------------------------------------------------
----------
David Parker    Tazz Networks    (401) 709-5130
 


 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050421/203f2592/attachment.html