Message-ID: <4CCF1F49.5060809@abpni.co.uk>
Date: Mon, 01 Nov 2010 20:12:57 +0000
From: Jonathan Tripathy <jonnyt@abpni.co.uk>
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: Thomas Kellerer <spam_eater@gmx.net>, pgsql-general@postgresql.org
Subject: Re: Replication
References: <4CCF1AC4.6060800@abpni.co.uk> <ian6bg$1so$1@dough.gmane.org>
In-Reply-To: <ian6bg$1so$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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?