Re: Replication docs update - Mailing list pgsql-docs

From Magnus Hagander
Subject Re: Replication docs update
Date
Msg-id CABUevEyOtiTgkVWw4D_z7QbajgJzD_XnyzePqa8cgtnuv9SojQ@mail.gmail.com
Whole thread Raw
In response to Re: Replication docs update  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Replication docs update  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
On Wed, Mar 21, 2012 at 16:44, Bruce Momjian <bruce@momjian.us> wrote:
> On Wed, Mar 21, 2012 at 12:01:34PM +0100, Magnus Hagander wrote:
>> On Tue, Mar 20, 2012 at 22:26, Bruce Momjian <bruce@momjian.us> wrote:
>> > Our chapter, "Comparison of Different Solutions", needs an update to use
>> > our new streaming replication terminology, and an update to mention the
>> > synchronous option.
>> >
>> > Patch attached.  I would like to apply it to head and 9.1.
>>
>> Is it really a good idea to remove the name "hot standby" where you've
>> done so? It's a term that's pretty well set by now. Maybe instad "hot
>> standby using transaction log replication" instead of taking it away
>> completely?
>
> Well, hot/warm standby is really a side-feature of replication, not a
> replication technology itself.  WAL streaming is a replication

True. I'm just saying it's a term that many are familiar with, and
thus removing it doesn't entirely help. Removing PITR is a good idea
however :-)

> technology.  For example, Shared Disk Failover is technically a warm
> standby too.

Pretty sure Shared Disk qualifies as cold standby.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Replication docs update
Next
From: Bruce Momjian
Date:
Subject: Re: Replication docs update