From: | Jonathan Tripathy <jonnyt(at)abpni(dot)co(dot)uk> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication |
Date: | 2010-11-02 06:59:27 |
Message-ID: | 4CCFB6CF.4060006@abpni.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/11/10 01:56, Scott Marlowe wrote:
> 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
>
What is the difference between the "Hot-Standby" and "Warm-Standby"? Is
the only different that the "Hot-Standby" standby servers are read-only,
whereas the "Warm-Standby" standbys can't be queried at all?
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2010-11-02 07:53:09 | Re: Connection Pool |
Previous Message | Stefan Schwarzer | 2010-11-02 06:54:47 | Re: Problem with Crosstab (Concatenate Problem) |