Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 615051337B6E for ; Mon, 3 Jan 2011 13:36:33 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 28157-06 for ; Mon, 3 Jan 2011 17:36:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 9724C1337B7D for ; Mon, 3 Jan 2011 13:36:25 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Mon, 03 Jan 2011 11:36:25 -0600 Message-Id: <4D21B4AE0200002500038F48@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Mon, 03 Jan 2011 11:36:14 -0600 From: "Kevin Grittner" To: "Imre Oolberg" , Subject: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal References: <4D1C670E.1090408@auul.pri.ee> <4D21AC15.1010102@auul.pri.ee> In-Reply-To: <4D21AC15.1010102@auul.pri.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.61 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201101/11 X-Sequence-Number: 36451 Imre Oolberg wrote: > archive_command = 'test ! -f > /data/backup/postgresql/archive-logs/%f && > cp %p /data/backup/postgresql/archive-logs' I suppose that will work, but why not specify %f in the copy target? > I guess that my problem is probably that although my .backup file > says > > 000000010000000000000009.00000020.backup > START WAL LOCATION: 0/9000020 (file 000000010000000000000009) > STOP WAL LOCATION: 1/6325B2E0 (file 000000010000000100000063) > CHECKPOINT LOCATION: 0/A2C4908 > START TIME: 2011-01-03 11:32:17 EET > LABEL: test > STOP TIME: 2011-01-03 12:18:27 EET > > looking at the pg_ctl.log it starts reading wal logs beginning > with 000000010000000100000063 and not with > 000000010000000000000009 What did you have in your recovery.conf file? -Kevin