Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1F0AB9FB595 for ; Fri, 30 Mar 2007 12:35:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 60115-04 for ; Fri, 30 Mar 2007 12:35:34 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 57A5C9FB547 for ; Fri, 30 Mar 2007 12:35:35 -0300 (ADT) thread-index: Acdy4Rbyo05w3LgOSjCgKmAlRSRfNg== Received: from [192.168.0.22] ([85.211.147.35]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Mar 2007 11:35:47 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Subject: Re: trying to run PITR recovery From: "Simon Riggs" To: "Warren Little" Cc: In-Reply-To: <5F414061-9F03-4580-9CD7-1458BA942530@MeridiasCapital.com> References: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> <1175253394.4386.745.camel@silverbirch.site> <5F414061-9F03-4580-9CD7-1458BA942530@MeridiasCapital.com> Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 30 Mar 2007 16:31:46 +0100 Message-ID: <1175268707.4386.778.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Mar 2007 15:35:48.0093 (UTC) FILETIME=[16E912D0:01C772E1] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/235 X-Sequence-Number: 25059 On Fri, 2007-03-30 at 08:23 -0600, Warren Little wrote: > On slightly different topic, is there some way to determine the > timeline of the corrupted segment, ie what was the original time of > the last restored transaction. You need to examine the WAL files using xlogdump available from pgfoundry.org - its not part of the main distribution yet. Reporting the time of the last commit/abort record seen in the WAL seems like an easy and useful addition to make. e.g. LOG: last transaction originally completed at 2007-02-23 05:57:35 Point-in-time recovery really ought to tell you the point-in-time it has stopped at sounds blindingly obvious in retrospect. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com