Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 8929B9FB546 for ; Sun, 5 Aug 2007 17:57:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 32397-07 for ; Sun, 5 Aug 2007 17:57:47 -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 472039FB509 for ; Sun, 5 Aug 2007 17:57:47 -0300 (ADT) thread-index: AcfXo05GuDWMGKK+RKKfeNpyO48FPA== Content-Class: urn:content-classes:message Received: from [192.168.0.5] ([81.6.216.155]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 5 Aug 2007 16:57:59 -0400 Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4073 Subject: Re: WAL segment question From: "Simon Riggs" To: "Donald Fraser" Cc: "[ADMIN]" In-Reply-To: <008601c7d622$244237a0$b464a8c0@demolish1> References: <008601c7d622$244237a0$b464a8c0@demolish1> Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 05 Aug 2007 21:58:49 +0100 Message-ID: <1186347529.4146.6.camel@ebony.site> MIME-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Aug 2007 20:57:59.0343 (UTC) FILETIME=[4E1BBBF0:01C7D7A3] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/29 X-Sequence-Number: 26360 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