Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B3605632C71 for ; Wed, 24 Mar 2010 14:19:30 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 01279-10 for ; Wed, 24 Mar 2010 17:19:20 +0000 (UTC) X-Greylist: delayed 00:08:47.854236 by SQLgrey-1.7.6 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by mail.postgresql.org (Postfix) with ESMTP id 560A863278C for ; Wed, 24 Mar 2010 14:19:20 -0300 (ADT) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 7A3FE118DCA; Wed, 24 Mar 2010 13:10:31 -0400 (EDT) Date: Wed, 24 Mar 2010 13:10:31 -0400 From: Ray Stell To: pgsql-admin@postgresql.org Subject: 8.2.15 pitr/00000001.history Message-ID: <20100324171031.GA13674@cns.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.74 tagged_above=-10 required=5 tests=BAYES_20=-0.74 X-Spam-Level: X-Archive-Number: 201003/183 X-Sequence-Number: 33982 While testing an 8.2.15 pitr procedure I see this postmaster log entry on startup of the recovered cluster: 2010-03-24 12:38:36.357 EDT,,3,,, LOG: restore_command = "cp /home/postgresql/fms/wals/%f %p" cp: cannot stat `/home/postgresql/fms/wals/00000001.history': No such file or directory pg goes on to restore from other wal segments, but I wonder if someone could explain the significance of this history file? Should I have such a file? Also, are there objects I can query to check the current cluster status compared to the beginning of the recovery for such things as next transaction ID, next OID, checkpoint record, and redo record? 2010-03-24 12:38:36.438 EDT,,6,,, LOG: checkpoint record is at 28/D9000020 2010-03-24 12:38:36.438 EDT,,7,,, LOG: redo record is at 28/D9000020; undo record is at 0/0; shutdown FALSE 2010-03-24 12:38:36.438 EDT,,8,,, LOG: next transaction ID: 0/9160987; next OID: 16874 Thanks.