pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Vick Khera <vivek@khera.org>
To: pgsql-general@postgresql.org
Subject: Re: Replication
Date: Mon, 01 Nov 2010 22:39:03 +0000
Message-ID: <4CCF4187.8010205@abpni.co.uk> (raw)
In-Reply-To: <AANLkTin8x5EruxEser40veOzq8_kGWbaQ7VkPy0H=hXM@mail.gmail.com>
References: <4CCF1AC4.6060800@abpni.co.uk>
	<AANLkTin8x5EruxEser40veOzq8_kGWbaQ7VkPy0H=hXM@mail.gmail.com>


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?



view thread (131+ messages)  latest in thread

Message-ID: <4CCF4187.8010205@abpni.co.uk>
Permalink:  ../4CCF4187.8010205@abpni.co.uk/
Also on:    postgresql.org/message-id/4CCF4187.8010205@abpni.co.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: jonnyt@abpni.co.uk, vivek@khera.org
  Subject: Re: Replication
  In-Reply-To: <4CCF4187.8010205@abpni.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox