From: | Bill MacArthur <webmaster(at)dhs-club(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | how to tell if a replication server has stopped replicating |
Date: | 2011-08-26 16:20:44 |
Message-ID: | 4E57C7DC.7020508@dhs-club.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
We recently discovered, quite by accident, that our streaming replication server was no longer replicating. We noticed this in our master server log file:
2011-08-26 00:00:05 PDT postgres 192.168.17.4 [unknown]LOG: replication connection authorized: user=postgres host=192.168.17.4 port=53542
2011-08-26 00:00:05 PDT postgres 192.168.17.4 [unknown]FATAL: requested WAL segment 00000001000001D10000006B has already been removed
As it turned out this has been going on for at least a week as everyday's log files were crammed with these messages. Whatever caused the replication server to end up needing the WAL file is a mystery for another day. What I would like to do is setup a simple method of alerting us if replication stops. We could do a simple grep of log files on the replication side, but I am guessing that there is some SQL command that could be run against the postgres internals that would be cleaner. Is there such an animal?
Thank you,
Bill MacArthur
From | Date | Subject | |
---|---|---|---|
Next Message | gais | 2011-08-26 16:21:45 | Point-In-Time Recovery not working |
Previous Message | Kevin Grittner | 2011-08-26 15:25:22 | Re: problem during installation of pgpool-Admin-3.0.3 |