Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D2E912E0031 for ; Fri, 16 May 2008 14:34:49 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 73876-05 for ; Fri, 16 May 2008 14:34:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail128073.authsmtp.com (outmail128073.authsmtp.com [62.13.128.73]) by developer.postgresql.org (Postfix) with ESMTP id 3FFA72E002F for ; Fri, 16 May 2008 14:34:46 -0300 (ADT) Received: from mail-c188.authsmtp.com (mail-c188.authsmtp.com [62.13.128.25]) by punt4.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id m4GHYgtG093392; Fri, 16 May 2008 18:34:42 +0100 (BST) Received: from [192.168.0.6] (85-211-226-243.dyn.gotadsl.co.uk [85.211.226.243]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id m4GHYf2Q029723; Fri, 16 May 2008 18:34:41 +0100 (BST) Subject: Re: error message in PITR restore: From: Simon Riggs To: Mark Steben Cc: pgsql-admin@postgresql.org In-Reply-To: <007701c8b779$45c2a890$14010a0a@dei26g028575> References: <007701c8b779$45c2a890$14010a0a@dei26g028575> Content-Type: text/plain Date: Fri, 16 May 2008 18:36:22 +0100 Message-Id: <1210959382.18922.99.camel@ebony.site> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 5db4b17f-236e-11dd-aecc-001871e930f4 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadBtFaQNbYFhI HGQLW1xEUVV7Wmd/ bwsfZQBDYEtPQQdo VlZLRlFNFgB3AVJc AmlmO09wFgVEcXly ZghqXXYVWRAocRR8 RRhJF24AMHphaTRL TRENJFBJcANLdhhE P1l8VCUJLwdybGoL NiMWHhYEdThFMiNP CgQANkkbTktDHzh0 fzE+J301EFYZQD8+ fXQn X-Authentic-SMTP: 61633235383639.cat.dmpriest.net.uk:953/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system! X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/152 X-Sequence-Number: 29236 On Fri, 2008-05-16 at 13:21 -0400, Mark Steben wrote: > Simon, I think you uncovered the problem but I don't see anyway around > it Short of reloading the db from a pg_dump backup. Any suggestions > would Be appreciated. Thanks, Re-run the backup? Sounds safest. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support