Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7B14B1337999 for ; Tue, 2 Nov 2010 03:59:29 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 75312-07 for ; Tue, 2 Nov 2010 06:59:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from abpni.co.uk (unknown [92.27.106.173]) by mail.postgresql.org (Postfix) with ESMTP id 415A21337990 for ; Tue, 2 Nov 2010 03:59:20 -0300 (ADT) Received: from [10.87.0.130] ([10.87.0.130]) by abpni.co.uk with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Nov 2010 06:59:18 +0000 Message-ID: <4CCFB6CF.4060006@abpni.co.uk> Date: Tue, 02 Nov 2010 06:59:27 +0000 From: Jonathan Tripathy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Scott Marlowe , pgsql-general@postgresql.org Subject: Re: Replication References: <4CCF1AC4.6060800@abpni.co.uk> <4CCF4187.8010205@abpni.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Nov 2010 06:59:18.0866 (UTC) FILETIME=[78460B20:01CB7A5B] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.212 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, RDNS_NONE=0.793, SARE_SPEC_REPLICA=0.72 X-Spam-Level: *** X-Archive-Number: 201011/94 X-Sequence-Number: 169160 On 02/11/10 01:56, Scott Marlowe wrote: > On Mon, Nov 1, 2010 at 4:39 PM, Jonathan Tripathy wrote: >> On 01/11/10 21:10, Vick Khera wrote: >>> On Mon, Nov 1, 2010 at 3:53 PM, Jonathan Tripathy >>> wrote: >>>> The standby must support INSERTS and UPDATES as well (once the master has >>>> failed) >>>> >>>> Are there any solutions like this? Looking on the Postgresql site, all >>>> the >>>> standby solutions seem to be read only.. >>> If they are RO it is only while they are replicas, not masters. Once >>> the server is upgraded to the master role, it becomes RW. >>> >> So in the "Hot Standby" setup as described in >> http://www.postgresql.org/docs/current/static/hot-standby.html , how would I >> automatically make the slave a master? > I think you're looking for this: > http://www.postgresql.org/docs/current/static/warm-standby-failover.html > What is the difference between the "Hot-Standby" and "Warm-Standby"? Is the only different that the "Hot-Standby" standby servers are read-only, whereas the "Warm-Standby" standbys can't be queried at all? Thanks