From: Simon Riggs <simon@2ndquadrant.com>
To: Warren Little <Warren.Little@MeridiasCapital.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: trying to run PITR recovery
Date: Fri, 30 Mar 2007 16:31:46 +0100
Message-ID: <1175268707.4386.778.camel@silverbirch.site> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: simon@2ndquadrant.com, Warren.Little@MeridiasCapital.com
Subject: Re: trying to run PITR recovery
In-Reply-To: <1175268707.4386.778.camel@silverbirch.site>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox