replay doesn't catch up with receive on standby

From: Steven Parkes <smparkes(at)smparkes(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: replay doesn't catch up with receive on standby
Date: 2011-04-19 00:00:50
Message-ID: 4A9F5341-E6AC-45F9-A86F-90CD820FC840@smparkes.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is on 9.0.3: I've got two dbs running as standby to a main db. They start up fine and seem to think they're all caught up (by /var/log logs), but

SELECT pg_last_xlog_receive_location() AS receive, pg_last_xlog_replay_location() AS replay;

reports replay behind receive and it doesn't change. This is on both dbs.

Notably the main db isn't (wasn't) doing anything, so no new commits were causing things to move forward. I did a write to it and both slaves moved both their recieved and replay serial numbers up.

Is there a valid situation where an idle master/standby setup could remain with replay behind received indefinitely? (My nagios monitor isn't very happy with that (at present)) and before changing that I'd like to understand better what's going on.)

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2011-04-19 00:35:32 Re: Help - corruption issue?
Previous Message Tomas Vondra 2011-04-18 23:44:08 Re: Help - corruption issue?