Message-ID: <4CCF4187.8010205@abpni.co.uk>
Date: Mon, 01 Nov 2010 22:39:03 +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: Vick Khera <vivek@khera.org>, pgsql-general@postgresql.org
Subject: Re: Replication
References: <4CCF1AC4.6060800@abpni.co.uk>
	<AANLkTin8x5EruxEser40veOzq8_kGWbaQ7VkPy0H=hXM@mail.gmail.com>
In-Reply-To: <AANLkTin8x5EruxEser40veOzq8_kGWbaQ7VkPy0H=hXM@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 01/11/10 21:10, Vick Khera wrote:
> On Mon, Nov 1, 2010 at 3:53 PM, Jonathan Tripathy<jonnyt@abpni.co.uk>  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?