Tue Nov 19 13:20:45 PST 2013
- Previous message: [Slony1-general] measuring latency for log shipping
- Next message: [Slony1-general] Combining multi-master PG 9.3 with slony1 replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11/19/13 09:13, Mike James wrote: > I am using slony1 log-shipping to replicate some data to a remote > location thru a VPN tunnel. A cron job running every minute applies the > logs to the remote slave. So the latency is at least one minute. Is > there a way to more precisely measure the latency between the origin and > slave? Log shipping replicas are not known to the origin of a set. There are no sl_confirm records for them. Only the slon deamon, writing the log shipping files, knows that it is doing so. That node is by design a replica itself and even it has no knowledge about who is possibly consuming those log shipping files. To determine the lag between the "origin" and a replica you need to know the current time on the origin and the timestamp of the last SYNC event from that origin replicated to the replica. Since log shipping replicas have no sl_confirm records, there is nothing inside the Slony system that could answer that question. Jan > > Thanks, > Mike > > > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] measuring latency for log shipping
- Next message: [Slony1-general] Combining multi-master PG 9.3 with slony1 replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list