Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 314629FA3AF for ; Tue, 28 Aug 2007 18:40:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 49962-03 for ; Tue, 28 Aug 2007 18:39:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by postgresql.org (Postfix) with ESMTP id 21D539FB4D5 for ; Tue, 28 Aug 2007 18:39:57 -0300 (ADT) Received: from new-host.home ([71.179.23.138]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JNI001BV6UCOV6H@vms046.mailsrvcs.net> for pgsql-admin@postgresql.org; Tue, 28 Aug 2007 16:39:49 -0500 (CDT) Date: Tue, 28 Aug 2007 17:39:33 -0400 From: Robert Treat Subject: Re: how is pitr replay interruption time determined? In-reply-to: <10268.1188256622@sss.pgh.pa.us> To: Tom Lane Cc: pgsql-admin@postgresql.org Message-id: <200708281739.34094.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-15 Content-transfer-encoding: 7bit Content-disposition: inline References: <200708271742.57392.xzilla@users.sourceforge.net> <10268.1188256622@sss.pgh.pa.us> User-Agent: KMail/1.9.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/369 X-Sequence-Number: 26700 On Monday 27 August 2007 19:17, Tom Lane wrote: > Robert Treat writes: > > LOG: database system was interrupted while in recovery at log time > > 2007-07-30 19:17:37 EDT > > > > I am curious how this date is determined by postgres/pitr? > > It's the update timestamp in pg_control, which in essence is going to be > the completion time of the last checkpoint. If the crash was during WAL > recovery, as it seems to be, it'd be the time the last "restart" > checkpoint was made. > Is there some way to force checkpoints on a db doing wal replay? Also, I would think at a minimum that the last "restart" checkpoint would be akin to when the db was last started, but looking at my replay instance I see: pg_control last modified: Mon Aug 27 12:12:55 2007 Time of latest checkpoint: Mon Jul 30 19:17:37 2007 The first date is around the time I restarted the instance, the second is still a mystery to me. Perhaps I am misinterpreting your respone? -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL