Wed Feb 4 16:13:12 PST 2015
- Previous message: [Slony1-general] Slony monitoring, management
- Next message: [Slony1-general] sl_log_1 not truncated, could not lock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Feb 03, 2015 at 02:27:37PM -0800, Tory M Blue wrote: > happened to the hardware, the query node was healthy, but seemingly not > replicating (replication check , showed that the queried table was not > changing, when the other nodes saw the change). Not quite what you are asking for, but the check_postgres script has a nice feature that simply adds a row and sees how long it takes to reach one or more destinations. It's a great canary-in-the-coalmine kind of check that Slony is up and running and doing what it is supposed to do. https://bucardo.org/check_postgres/check_postgres.pl.html#replicate_row -- Greg Sabino Mullane greg at endpoint.com End Point Corporation PGP Key: 0x14964AC8 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 163 bytes Desc: Digital signature Url : http://lists.slony.info/pipermail/slony1-general/attachments/20150204/5151c80f/attachment.pgp
- Previous message: [Slony1-general] Slony monitoring, management
- Next message: [Slony1-general] sl_log_1 not truncated, could not lock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list