On Tue, Apr 19, 2011 at 9:00 AM, Steven Parkes <smpar...@smparkes.net> wrote: > 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.)
Did you run query on the standby? If yes, I guess that query conflict prevented the reply location from advancing. http://www.postgresql.org/docs/9.0/static/hot-standby.html#HOT-STANDBY-CONFLICT Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
