From: Simon Riggs <simon@2ndquadrant.com>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: WAL segment question
Date: Sun, 05 Aug 2007 21:58:49 +0100
Message-ID: <1186347529.4146.6.camel@ebony.site> (raw)
In-Reply-To: <008601c7d622$244237a0$b464a8c0@demolish1>
References: <008601c7d622$244237a0$b464a8c0@demolish1>
On Sat, 2007-08-04 at 00:00 +0100, Donald Fraser wrote:
> Our company has two sites, a master and a disaster recovery site.
> I am trying to assess whether data has been lost during a fail-over,
> due to the asynchronous method of transporting WAL file data between
> sites (we use DRBD).
>
> Disaster recovery node start-up log:
> user= pid=9907 timestamp=[2007-08-01 17:09:51 BST] tid= LOG: record
> with zero length at 0/7C62F52C
> user= pid=9907 timestamp=[2007-08-01 17:09:51 BST] tid= LOG: redo
> done at 0/7C62F4E8
>
> My question is: given the above WAL segment information, can I use it
> to decide whether information was lost in the master database site, at
> the point of failure, without starting the database up?
Currently there is no built-in means of finding out the time of the last
record transferred, if the primary stays down. You need to use xlogdump
to locate the time of the last commit/abort record.
--
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, postgres@kiwi-fraser.net
Subject: Re: WAL segment question
In-Reply-To: <1186347529.4146.6.camel@ebony.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