From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-general@postgresql.org
Subject: Re: Replication
Date: Mon, 01 Nov 2010 20:29:28 +0000
Message-ID: <4CCF2328.4030701@abpni.co.uk> (raw)
In-Reply-To: <ian7pn$8m1$1@dough.gmane.org>
References: <4CCF1AC4.6060800@abpni.co.uk>
<ian6bg$1so$1@dough.gmane.org>
<4CCF1F49.5060809@abpni.co.uk>
<ian7pn$8m1$1@dough.gmane.org>
On 01/11/10 20:26, Thomas Kellerer wrote:
> Jonathan Tripathy wrote on 01.11.2010 21:12:
>>>
>>> 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
>>>
>>>
>>>
>> But does that not only allow "read-only" things to work on the standby?
>>
>
> But you didn't ask for read/write on the standby, only for a standby
> that can take of the master once the master fails:
> "must support INSERTS and UPDATES as well (once the master has failed)"
>
> That's exactly what the hot standby does: As long as it is in standby
> mode it's read-only.
> Once the failover has happened the standby is the new master and will
> allow read/write access.
>
> Thomas
>
>
Ahh!! So in both those links above, once the master has failed, the
standby will support writes (As it not acts like the master)?
Thanks
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, spam_eater@gmx.net
Subject: Re: Replication
In-Reply-To: <4CCF2328.4030701@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