Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id DC0411337B5E for ; Mon, 1 Nov 2010 17:28:08 -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 08841-07 for ; Mon, 1 Nov 2010 20:28:01 +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 3DD5E1337B51 for ; Mon, 1 Nov 2010 17:28:00 -0300 (ADT) Received: from [10.87.0.130] ([10.87.0.130]) by abpni.co.uk with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Nov 2010 20:27:59 +0000 Message-ID: <4CCF22D5.7020109@abpni.co.uk> Date: Mon, 01 Nov 2010 20:28:05 +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> <4CCF1F49.5060809@abpni.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Nov 2010 20:27:59.0096 (UTC) FILETIME=[462BD780:01CB7A03] 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/75 X-Sequence-Number: 169141 On 01/11/10 20:21, Scott Marlowe wrote: > On Mon, Nov 1, 2010 at 2:12 PM, Jonathan Tripathy wrote: >> On 01/11/10 20:01, Thomas Kellerer wrote: >>> Jonathan Tripathy wrote on 01.11.2010 20:53: >>>> Hi Everyone, >>>> >>>> I'm looking for the best solution for "Hot Standbys" where once the >>>> primary server fails, the standby will take over and act just like >>>> the master did. 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.. >>> 9.0 has streaming replication and "Hot Standby" >>> >>> http://www.postgresql.org/docs/current/static/hot-standby.html >>> >>> http://www.postgresql.org/docs/current/static/warm-standby.html#STREAMING-REPLICATION >>> >>> Regards >>> Thomas >>> >>> >>> >> But does that not only allow "read-only" things to work on the standby? > Yep. Generally when to fail over is considered a business decision. > I think only pgpool supports automatic failover but has a lot of > limitations to deal with otherwise. So really Postgresql doesn't have any "Hot Standbys" that once fail-over has occurred, the system can act as normal? For this, would I have to looking in Xen or VMWare HA? I'm guessing the standbys in the "warm-failover" setup allow write operations? Thanks