On Mon, Jun 18, 2007 at 10:14:16AM -0500, Jeff Amiel wrote:

> I removed the node from replication (but I don't remember how...either 
> by dropping the node (via the "Replication' item in pgadmin) or some 
> other means)  Once our remote site access was restored, I re-added the 
> node (via slon script to set up the subscriptions properly).  I remember 
> this being only a few hours later.  I apparently didn't check to see if 
> it was properly replicating.

Well, if you unsubscribed and then later resubscribed, AFAIK the
whole dump-restore business would have happened, so you wouldn't be
missing anything.  So I have a feeling. . .

> no_active set to 'false' for that node.  I then used a couple of slony 
> functions to re-enable the node....and replication begin again.

. . .that when you did this you re-enabled the subscription of
someone who had been completely unsubscribed on the origin.  Or
something.  Remember, you have to run these functions on both ends of
the connection.  Perhaps your origin still actually has the data
destined for that node (but I doubt it, or else you wouldn't have a
gap, since it'd all get applied in order).

> take a node offline and bring it back online would be helpful.  What IS 
> the proper way to temporarily drop a node and then re-enable it later?

Stop the slon.  That's what sends the data.  The data will just build
up at the origin, and all get applied when it's time to do so.

A

-- 
Andrew Sullivan  | ajs at crankycanuck.ca
Unfortunately reformatting the Internet is a little more painful 
than reformatting your hard drive when it gets out of whack.
		--Scott Morris