Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4BDBA9FB429 for ; Mon, 27 Aug 2007 18:43:30 -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 86612-02-7 for ; Mon, 27 Aug 2007 18:43:21 -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 5508C9FB3D6 for ; Mon, 27 Aug 2007 18:43:25 -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 <0JNG00FXICBXGIFC@vms046.mailsrvcs.net> for pgsql-admin@postgresql.org; Mon, 27 Aug 2007 16:43:10 -0500 (CDT) Date: Mon, 27 Aug 2007 17:42:57 -0400 From: Robert Treat Subject: how is pitr replay interruption time determined? To: pgsql-admin@postgresql.org Message-id: <200708271742.57392.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline User-Agent: KMail/1.9.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/335 X-Sequence-Number: 26666 Today I was running some tests on one of our warm standbys. The way this test works is I took a zfs snapshot of the filesystem, induce failover, of the pitr host, then log in and play around with the data. Once we're done with this, I rolled back the zfs snapshot, restart the standby instance, and let it start doing wal_replay again. All of this seems to work fine, but when I start the replay instance again I get the following line in my logfile: 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? The standby had processed wal_logs right through today before having taken the zfs snapshot, so I would think it would have been interrupted at a log time of sometime today. Also the initial replay setup occured sometime was long before 07-30, so that doesn't correspond to that date either, so I'm wondering what it is that determines the point in time that replay thinks it is interuppted at. FWIW, this does have practical implecations, like how many wal files to keep around, in my case I had all the files going back to that date, so I only had to wait for replay to catch up.... 5 hours later :-). But it would be good to be able to predetermine that kind of thing. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL