Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 696619FC589 for ; Fri, 1 Jun 2007 17:04:11 -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 09753-03 for ; Fri, 1 Jun 2007 17:04:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id BBBF99FC4A5 for ; Fri, 1 Jun 2007 17:04:05 -0300 (ADT) Thread-Index: AcekiApEGpJtmIuoSqeyfKEuBk/p+Q== Received: from [192.168.0.4] ([85.211.69.99]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Jun 2007 16:04:17 -0400 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Importance: normal Subject: Re: Attempt to re-archive existing WAL logs afterrestoringfrom backup From: "Simon Riggs" To: "Jon Colverson" Cc: In-Reply-To: <1180695755.26297.101.camel@silverbirch.site> References: <465BA7C5.6080400@vcxz.co.uk> <465E55F2.2020103@vcxz.co.uk> <28998.1180620113@sss.pgh.pa.us> <465EE541.3020501@vcxz.co.uk> <1180695755.26297.101.camel@silverbirch.site> Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 01 Jun 2007 21:02:19 +0100 Message-ID: <1180728140.26297.261.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Jun 2007 20:04:17.0906 (UTC) FILETIME=[0921B520:01C7A488] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/8 X-Sequence-Number: 25676 On Fri, 2007-06-01 at 12:02 +0100, Simon Riggs wrote: > On Thu, 2007-05-31 at 16:09 +0100, Jon Colverson wrote: > > > > > >> This looks like a bug to me. Any thoughts? > > > > > > No; nothing is touching the archive except for the archive_command being > > run by PostgreSQL. > > Jon, > > You're still troubled by what you've seen? > > Can you start from the beginning again and describe exactly what set of > circumstances you're in. I want to remove any bug or doubt that there is > one lurking. I've spent some time re-examining the code and I can't see a route for the discussed problem to occur. All the main code paths do not exhibit this problem in 8.2, so I'm not sure where to go from here. If you can help further, please give me a shout. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com