Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1FFBE9FB487 for ; Tue, 24 Apr 2007 06:31:18 -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 92659-02 for ; Tue, 24 Apr 2007 06:31:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by postgresql.org (Postfix) with ESMTP id 5E1C59FB88D for ; Tue, 24 Apr 2007 06:31:13 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id a73so1548847pye for ; Tue, 24 Apr 2007 02:31:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KDTXsWsZOU//7Cs/AVGQ1kytuKglv3OYz8xV+dfHzshmAGJDC4Wlt/GMynFB+xCvF/LyFMH6ZwzeMBQOnCW7e1dfT4dk6w1NUzIzWZVHtBV/IXa4Q8qfk4sQDfZ6OhVtEr6LAJezjkMp0rzsUl1zRBn5jloD1avPRpIKOYNB4Yg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=eD3t0j/hDCuYFRoXoohDnHDUXFHSWMxQy5cEIAMQWD4R3tjMr1+SjffffVXm+TxG3E9kXMkGZ2Ympni1/EHYp0xpcR0dB9ocnD/FmFGTN52QyoC3QOyQqNHFAaXI6FTPXf4VHStnX/pP3vo5VZjThrnLqyGvquqq9EMHP9qOiWw= Received: by 10.65.241.20 with SMTP id t20mr13999742qbr.1177407071778; Tue, 24 Apr 2007 02:31:11 -0700 (PDT) Received: by 10.65.177.7 with HTTP; Tue, 24 Apr 2007 02:31:11 -0700 (PDT) Message-ID: <88daf38c0704240231s347ae29du220fec6443a59d88@mail.gmail.com> Date: Tue, 24 Apr 2007 11:31:11 +0200 From: "Alexander Staubo" To: Mageshwaran , pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] Regarding WAL In-Reply-To: <88daf38c0704240229g3cb2ddcajc97af5892fa72605@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462D7A64.2010308@sifycorp.com> <88daf38c0704240229g3cb2ddcajc97af5892fa72605@mail.gmail.com> X-Google-Sender-Auth: 686620b89e99b27b X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/215 X-Sequence-Number: 25279 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 Alexander.