Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 00F419FBE03; Wed, 25 Apr 2007 12:34:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 24643-06; Wed, 25 Apr 2007 12:34:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (webmail.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 9A5C19FBE16; Wed, 25 Apr 2007 12:34:33 -0300 (ADT) thread-index: AceHT0HEWfHqLIW0Rz629JBU+Rp7fg== Received: from [172.24.32.25] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Apr 2007 11:34:46 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Subject: Re: [GENERAL] Regarding WAL From: "Simon Riggs" To: "Alexander Staubo" Cc: "Mageshwaran" , , In-Reply-To: <88daf38c0704240231s347ae29du220fec6443a59d88@mail.gmail.com> References: <462D7A64.2010308@sifycorp.com> <88daf38c0704240229g3cb2ddcajc97af5892fa72605@mail.gmail.com> <88daf38c0704240231s347ae29du220fec6443a59d88@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 25 Apr 2007 16:24:05 +0100 Message-ID: <1177514645.20637.143.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Apr 2007 15:34:47.0031 (UTC) FILETIME=[41414070:01C7874F] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/232 X-Sequence-Number: 25296 On Tue, 2007-04-24 at 11:31 +0200, Alexander Staubo wrote: > On 4/24/07, Mageshwaran wrote: > > I want to do replication using WAL , please tell the methods by which > > log shipping is done ie moving the wal files to slaves and executing it. > > Not possible at the moment: the log shipping facility that was > introduced in 8.2 only lets you set up a so-called warm standby, which > cannot be queried; it's not live replication. > > The warm standby system is a fairly crude hack that relies on WAL > files being copied from the main server to the standby and then > starting the standby in recovery mode when you want to bring it up. At > this point the standby is your main database, and it can no longer WAL > files. Documented here: > > http://www.postgresql.org/docs/8.2/static/warm-standby.html The use-case for Warm Standby is for people that want a simple, efficient mechanism for providing High Availability replication. If there are any feature requests, please let me know. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com