Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 67E891337B59 for ; Mon, 1 Nov 2010 17:02:16 -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 92387-06 for ; Mon, 1 Nov 2010 20:02:09 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 1842E1337B3E for ; Mon, 1 Nov 2010 17:02:08 -0300 (ADT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PD0Zz-0002S3-34 for pgsql-general@postgresql.org; Mon, 01 Nov 2010 21:02:07 +0100 Received: from ppp-188-174-123-26.dynamic.mnet-online.de ([188.174.123.26]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Nov 2010 21:02:07 +0100 Received: from spam_eater by ppp-188-174-123-26.dynamic.mnet-online.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Nov 2010 21:02:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-general@postgresql.org From: Thomas Kellerer Subject: Re: Replication Date: Mon, 01 Nov 2010 21:01:59 +0100 Lines: 19 Message-ID: References: <4CCF1AC4.6060800@abpni.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ppp-188-174-123-26.dynamic.mnet-online.de User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666 In-Reply-To: <4CCF1AC4.6060800@abpni.co.uk> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.409 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, SARE_SPEC_REPLICA=0.72, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: ** X-Archive-Number: 201011/66 X-Sequence-Number: 169132 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