Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 274C79F9A95 for ; Tue, 28 Aug 2007 18:59:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 60528-08 for ; Tue, 28 Aug 2007 18:59:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id BED0B9F9295 for ; Tue, 28 Aug 2007 18:59:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7SLxK6Y004556; Tue, 28 Aug 2007 17:59:20 -0400 (EDT) To: Robert Treat cc: pgsql-admin@postgresql.org, Simon Riggs Subject: Re: how is pitr replay interruption time determined? In-reply-to: <200708281739.34094.xzilla@users.sourceforge.net> References: <200708271742.57392.xzilla@users.sourceforge.net> <10268.1188256622@sss.pgh.pa.us> <200708281739.34094.xzilla@users.sourceforge.net> Comments: In-reply-to Robert Treat message dated "Tue, 28 Aug 2007 17:39:33 -0400" Date: Tue, 28 Aug 2007 17:59:20 -0400 Message-ID: <4555.1188338360@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/370 X-Sequence-Number: 26701 Robert Treat writes: > Is there some way to force checkpoints on a db doing wal replay? No, it's hardwired to do it when it sees a checkpoint record in the WAL stream. > pg_control last modified: Mon Aug 27 12:12:55 2007 > Time of latest checkpoint: Mon Jul 30 19:17:37 2007 After looking again at the code, the "last modified" time is the time that a recovery checkpoint was last done, and the "latest checkpoint" is the timestamp of the WAL-stream checkpoint record that triggered it. In a situation where you're catching up on historical WAL they could be far apart, but when a slave is just following the master there shouldn't be a huge difference --- not more than the maximum time to fill a WAL record and ship it over to the slave, for sure. (BTW, I misread it before --- it looks like the "at log time" value printed at startup *is* taken from the checkpoint record that it's trying to roll forward from.) Assuming that you're absorbing data from the master at a steady rate, the only reason I can see for the timestamps to be so old is if the "rm_safe_restartpoint" checks are always failing. I seem to remember that we found and fixed a bug that could cause something like that, but I can't find any trace of it in the CVS logs. Simon, do you recall such a problem post-8.2.0? regards, tom lane