From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Jonathan Tripathy <jonnyt(at)abpni(dot)co(dot)uk> |
Cc: | Vick Khera <vivek(at)khera(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication |
Date: | 2010-11-02 01:56:44 |
Message-ID: | AANLkTingS59Fep3u-JoDw77oauoqu2inBffPCuCNxxdr@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Nov 1, 2010 at 4:39 PM, Jonathan Tripathy <jonnyt(at)abpni(dot)co(dot)uk> wrote:
>
> On 01/11/10 21:10, Vick Khera wrote:
>>
>> On Mon, Nov 1, 2010 at 3:53 PM, Jonathan Tripathy<jonnyt(at)abpni(dot)co(dot)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?
I think you're looking for this:
http://www.postgresql.org/docs/current/static/warm-standby-failover.html
--
To understand recursion, one must first understand recursion.
From | Date | Subject | |
---|---|---|---|
Next Message | zab08 | 2010-11-02 02:36:57 | Re: select problem |
Previous Message | Tom Lane | 2010-11-01 23:04:54 | Re: can select contents of view but not view itself, despite indirect membership |