Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id C5E6C9FB45A for ; Fri, 3 Aug 2007 20:19: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 32035-08 for ; Fri, 3 Aug 2007 20:18:58 -0300 (ADT) X-Greylist: delayed 00:18:24.398697 by SQLgrey-1.7.5 Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by postgresql.org (Postfix) with ESMTP id ACFCE9FB35E for ; Fri, 3 Aug 2007 20:19:08 -0300 (ADT) Received: from [172.23.170.136] (helo=anti-virus01-07) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1IH68Q-00030m-L5 for pgsql-admin@postgresql.org; Sat, 04 Aug 2007 00:00:42 +0100 Received: from [82.44.23.191] (helo=demolish1) by asmtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1IH68Q-0003Tb-5f for pgsql-admin@postgresql.org; Sat, 04 Aug 2007 00:00:42 +0100 Message-ID: <008601c7d622$244237a0$b464a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" Subject: WAL segment question Date: Sat, 4 Aug 2007 00:00:52 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01C7D62A.85E2EB00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.243 tagged_above=0 required=5 tests=AWL=0.241, BAYES_50=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200708/24 X-Sequence-Number: 26355 This is a multi-part message in MIME format. ------=_NextPart_000_0083_01C7D62A.85E2EB00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=3D pid=3D9907 timestamp=3D[2007-08-01 17:09:51 BST] tid=3D LOG: = record with zero length at 0/7C62F52C user=3D pid=3D9907 timestamp=3D[2007-08-01 17:09:51 BST] tid=3D 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? Regards Donald Fraser. ------=_NextPart_000_0083_01C7D62A.85E2EB00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Our company has two sites, a master and a disaster = recovery=20 site.
I am trying to assess whether data has been lost = during a=20 fail-over, due to the asynchronous method of transporting WAL file=20 data between sites (we use DRBD).
 
Disaster recovery node start-up log:
user=3D pid=3D9907 timestamp=3D[2007-08-01 17:09:51 = BST] tid=3D=20 LOG:  record with zero length at 0/7C62F52C
user=3D pid=3D9907=20 timestamp=3D[2007-08-01 17:09:51 BST] tid=3D LOG:  redo done at=20 0/7C62F4E8
 
My question is: given the = above WAL=20 segment information, can I use it to decide whether information was lost = in the=20 master database site, at the point of = failure, without=20 starting the database up?
 
Regards
Donald Fraser.
 
 
------=_NextPart_000_0083_01C7D62A.85E2EB00--