Sorry,

What I mean by "done replicating changes" is that Slony has finished replicating the changes we just made to the master database to the slave database we are currently working with.

Our process is to stop Slony on all servers, remove the replication engine for our live database, restart Slony so the other database we are replicating can finish, make the changes to the master, then add the engine back to the master & one slave, restart Slony on them and then we need a way to tell that the changes have made it to that slave before we move on to the next slave.

Shaun McCloud – Associate Software Developer
Geo-Comm, Inc
601 W. Saint Germain St., Saint Cloud, MN 56301
Office: 320.240.0040 Fax: 320.240.2389 Toll Free: 888.436.2666
click here to visit www.geo-comm.com
 
 Think before you print!
Microsoft Certified Desktop Support Technician (MCDST)

-----Original Message-----
From: Greg Sabino Mullane [mailto:greg at endpoint.com] 
Sent: Wednesday, April 04, 2012 16:45
To: Shaun McCloud
Cc: slony1-general at lists.slony.info
Subject: Re: [Slony1-general] Query to see when Slony is done replicating changes?

On Tue, Apr 03, 2012 at 05:51:58PM +0000, Shaun McCloud wrote:
> I'm wondering if its possible to query any of the databases in my 
> cluster to see when Slony is done replicating changes to a single 
> node.

It might help to expand on what you mean exactly by "done replicating changes", as replication is an ongoing process, but you could use the replicate_row action of check_postgres.pl:

http://bucardo.org/check_postgres/check_postgres.pl.html

Since Slony does things in order, you know that if this check works, the node is "caught up" and has finished anything that might have been going on before the check started. It simply flips a value on a replicated table and reports back how long until that value propagates to another slave (or slaves).

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8