To: pgsql-general@postgresql.org
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: Replication
Date: Mon, 01 Nov 2010 21:26:38 +0100
Lines: 18
Message-ID: <ian7pn$8m1$1@dough.gmane.org>
References: <4CCF1AC4.6060800@abpni.co.uk> <ian6bg$1so$1@dough.gmane.org>
	<4CCF1F49.5060809@abpni.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: <4CCF1F49.5060809@abpni.co.uk>

Jonathan Tripathy wrote on 01.11.2010 21:12:
>>
>> 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
>>
>>
> But does that not only allow "read-only" things to work on the standby?
>

But you didn't ask for read/write on the standby, only for a standby that can take of the master once the master fails:
"must support INSERTS and UPDATES as well (once the master has failed)"

That's exactly what the hot standby does: As long as it is in standby mode it's read-only.
Once the failover has happened the standby is the new master and will allow read/write access.

Thomas