| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Jonathan Tripathy <jonnyt(at)abpni(dot)co(dot)uk> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Replication |
| Date: | 2010-11-01 20:21:14 |
| Message-ID: | AANLkTik+TT22C2iPOLVO9J3Tv6sCojjQ_CaT61oKb4A1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 1, 2010 at 2:12 PM, Jonathan Tripathy <jonnyt(at)abpni(dot)co(dot)uk> wrote:
>
> On 01/11/10 20:01, Thomas Kellerer wrote:
>>
>> Jonathan Tripathy wrote on 01.11.2010 20:53:
>>>
>>> Hi Everyone,
>>>
>>> I'm looking for the best solution for "Hot Standbys" where once the
>>> primary server fails, the standby will take over and act just like
>>> the master did. 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..
>>
>> 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
>>
>> Regards
>> Thomas
>>
>>
>>
> But does that not only allow "read-only" things to work on the standby?
Yep. Generally when to fail over is considered a business decision.
I think only pgpool supports automatic failover but has a lot of
limitations to deal with otherwise.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-11-01 20:22:37 | Re: async queries in Perl and poll()/select() loop - how to make them work together? |
| Previous Message | Merlin Moncure | 2010-11-01 20:13:20 | Re: Temporary schemas |