Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5CD5C9FB52E for ; Mon, 6 Aug 2007 20:59:24 -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 83085-09 for ; Mon, 6 Aug 2007 20:59:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by postgresql.org (Postfix) with ESMTP id C3D169FB4E6 for ; Mon, 6 Aug 2007 20:59:20 -0300 (ADT) Received: from [172.23.170.140] (helo=anti-virus02-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1IICTm-0003s1-IT for pgsql-admin@postgresql.org; Tue, 07 Aug 2007 00:59:18 +0100 Received: from [82.44.23.191] (helo=demolish1) by asmtp-out6.blueyonder.co.uk with smtp (Exim 4.52) id 1IICTm-0008Tw-23 for pgsql-admin@postgresql.org; Tue, 07 Aug 2007 00:59:18 +0100 Message-ID: <00f201c7d885$d50a9900$b464a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" References: <008601c7d622$244237a0$b464a8c0@demolish1> <46B7A6A6.9010401@otg-nc.com> Subject: Re: WAL segment question Date: Tue, 7 Aug 2007 00:59:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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-Archive-Number: 200708/35 X-Sequence-Number: 26366 ----- Original Message ----- From: Chander Ganesan > DRBD is a synchronous method of transferring data - it's not asynchronous. Assuming you are using Protocol C you should find that both are always in sync. If you are using protocol B then things will be in sync so long as the remote system didn't crash, and if you are using Protocol A then things should be in sync as long as the local system didn't crash. Apologies if you thought I was insinuating DRBD is categorically asynchronous. But you assumed wrong, we use protocol A, because we don't have a fast WAN link < 10Mbps. According to the DRBD documentation: Protocol A: write IO is reported as completed, if it has reached local disk and local tcp send buffer. Which I interpret as: A for Asynchronous, which means I can complete writing data and start writing the next set of data before the first set of data has been synchronised at the remote site. This is the cost of our system - we are willing to loose data for improved performance of our master server. We've had one failure in 7 years that I've been at the company... Many thanks to Linux and more importantly PostgreSQL! One day when our local telecomms company stop the monopoly on leased data lines, we may upgrade our DR link to a 100Mbps or even 1Gbps link, in which case, protocol B or C will be a better solution. Unfortunately I think there's a better chance that the cost of postage will go down first.