pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedReplication docs update
6+ messages / 2 participants
[nested] [flat]
* Replication docs update
@ 2012-03-20 21:26 Bruce Momjian <bruce@momjian.us>
2012-03-21 11:01 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
2012-04-09 18:40 ` Re: Replication docs update Bruce Momjian <bruce@momjian.us>
0 siblings, 2 replies; 6+ messages in thread
From: Bruce Momjian @ 2012-03-20 21:26 UTC (permalink / raw)
To: pgsql-docs
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.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachments:
repl_doc.diff (text/x-diff, 5.5K) download
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
new file mode 100644
index ed34dac..e4f2e01
*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
*************** protocol to make nodes agree on a serial
*** 140,146 ****
</varlistentry>
<varlistentry>
! <term>Warm and Hot Standby Using Point-In-Time Recovery (<acronym>PITR</>)</term>
<listitem>
<para>
--- 140,146 ----
</varlistentry>
<varlistentry>
! <term>Transaction Log Shipping</term>
<listitem>
<para>
*************** protocol to make nodes agree on a serial
*** 148,158 ****
stream of write-ahead log (<acronym>WAL</>)
records. If the main server fails, the standby contains
almost all of the data of the main server, and can be quickly
! made the new master database server. This is asynchronous and
! can only be done for the entire database server.
</para>
<para>
! A PITR standby server can be implemented using file-based log shipping
(<xref linkend="warm-standby">) or streaming replication (see
<xref linkend="streaming-replication">), or a combination of both. For
information on hot standby, see <xref linkend="hot-standby">.
--- 148,158 ----
stream of write-ahead log (<acronym>WAL</>)
records. If the main server fails, the standby contains
almost all of the data of the main server, and can be quickly
! made the new master database server. This can be synchronous or
! asynchronous and can only be done for the entire database server.
</para>
<para>
! A standby server can be implemented using file-based log shipping
(<xref linkend="warm-standby">) or streaming replication (see
<xref linkend="streaming-replication">), or a combination of both. For
information on hot standby, see <xref linkend="hot-standby">.
*************** protocol to make nodes agree on a serial
*** 291,297 ****
<entry>Feature</entry>
<entry>Shared Disk Failover</entry>
<entry>File System Replication</entry>
! <entry>Hot/Warm Standby Using PITR</entry>
<entry>Trigger-Based Master-Standby Replication</entry>
<entry>Statement-Based Replication Middleware</entry>
<entry>Asynchronous Multimaster Replication</entry>
--- 291,297 ----
<entry>Feature</entry>
<entry>Shared Disk Failover</entry>
<entry>File System Replication</entry>
! <entry>Transaction Log Shipping</entry>
<entry>Trigger-Based Master-Standby Replication</entry>
<entry>Statement-Based Replication Middleware</entry>
<entry>Asynchronous Multimaster Replication</entry>
*************** protocol to make nodes agree on a serial
*** 305,311 ****
<entry>Most Common Implementation</entry>
<entry align="center">NAS</entry>
<entry align="center">DRBD</entry>
! <entry align="center">PITR</entry>
<entry align="center">Slony</entry>
<entry align="center">pgpool-II</entry>
<entry align="center">Bucardo</entry>
--- 305,311 ----
<entry>Most Common Implementation</entry>
<entry align="center">NAS</entry>
<entry align="center">DRBD</entry>
! <entry align="center">Streaming Repl.</entry>
<entry align="center">Slony</entry>
<entry align="center">pgpool-II</entry>
<entry align="center">Bucardo</entry>
*************** protocol to make nodes agree on a serial
*** 360,366 ****
<entry>No waiting for multiple servers</entry>
<entry align="center">•</entry>
<entry align="center"></entry>
! <entry align="center">•</entry>
<entry align="center">•</entry>
<entry align="center"></entry>
<entry align="center">•</entry>
--- 360,366 ----
<entry>No waiting for multiple servers</entry>
<entry align="center">•</entry>
<entry align="center"></entry>
! <entry align="center">with sync off</entry>
<entry align="center">•</entry>
<entry align="center"></entry>
<entry align="center">•</entry>
*************** protocol to make nodes agree on a serial
*** 371,377 ****
<entry>Master failure will never lose data</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
! <entry align="center"></entry>
<entry align="center"></entry>
<entry align="center">•</entry>
<entry align="center"></entry>
--- 371,377 ----
<entry>Master failure will never lose data</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
! <entry align="center">with sync on</entry>
<entry align="center"></entry>
<entry align="center">•</entry>
<entry align="center"></entry>
*************** protocol to make nodes agree on a serial
*** 382,388 ****
<entry>Standby accept read-only queries</entry>
<entry align="center"></entry>
<entry align="center"></entry>
! <entry align="center">Hot only</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
--- 382,388 ----
<entry>Standby accept read-only queries</entry>
<entry align="center"></entry>
<entry align="center"></entry>
! <entry align="center">with hot</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
<entry align="center">•</entry>
* Re: Replication docs update
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
@ 2012-03-21 11:01 ` Magnus Hagander <magnus@hagander.net>
2012-03-21 15:44 ` Re: Replication docs update Bruce Momjian <bruce@momjian.us>
1 sibling, 1 reply; 6+ messages in thread
From: Magnus Hagander @ 2012-03-21 11:01 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: pgsql-docs
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?
(And i'm sure Thom will find a bunch of typos, but there is no way
around that I think..)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Replication docs update
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
2012-03-21 11:01 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
@ 2012-03-21 15:44 ` Bruce Momjian <bruce@momjian.us>
2012-03-21 16:06 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
0 siblings, 1 reply; 6+ messages in thread
From: Bruce Momjian @ 2012-03-21 15:44 UTC (permalink / raw)
To: Magnus Hagander <magnus@hagander.net>; +Cc: pgsql-docs
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
technology. For example, Shared Disk Failover is technically a warm
standby too.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Replication docs update
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
2012-03-21 11:01 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
2012-03-21 15:44 ` Re: Replication docs update Bruce Momjian <bruce@momjian.us>
@ 2012-03-21 16:06 ` Magnus Hagander <magnus@hagander.net>
2012-03-21 17:16 ` Re: Replication docs update Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 6+ messages in thread
From: Magnus Hagander @ 2012-03-21 16:06 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: 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/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Replication docs update
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
2012-03-21 11:01 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
2012-03-21 15:44 ` Re: Replication docs update Bruce Momjian <bruce@momjian.us>
2012-03-21 16:06 ` Re: Replication docs update Magnus Hagander <magnus@hagander.net>
@ 2012-03-21 17:16 ` Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 6+ messages in thread
From: Bruce Momjian @ 2012-03-21 17:16 UTC (permalink / raw)
To: Magnus Hagander <magnus@hagander.net>; +Cc: pgsql-docs
On Wed, Mar 21, 2012 at 05:06:27PM +0100, Magnus Hagander wrote:
> 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 :-)
Well, the term doesn't help describe what it is, so familiar doesn't
help us much.
> > technology. For example, Shared Disk Failover is technically a warm
> > standby too.
>
> Pretty sure Shared Disk qualifies as cold standby.
Why is it cold? It can start up right away. What does warm mean then?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Replication docs update
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
@ 2012-04-09 18:40 ` Bruce Momjian <bruce@momjian.us>
1 sibling, 0 replies; 6+ messages in thread
From: Bruce Momjian @ 2012-04-09 18:40 UTC (permalink / raw)
To: pgsql-docs
On Tue, Mar 20, 2012 at 05:26:43PM -0400, Bruce Momjian 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.
Applied to head.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2012-04-09 18:40 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-03-20 21:26 Replication docs update Bruce Momjian <bruce@momjian.us>
2012-03-21 11:01 ` Magnus Hagander <magnus@hagander.net>
2012-03-21 15:44 ` Bruce Momjian <bruce@momjian.us>
2012-03-21 16:06 ` Magnus Hagander <magnus@hagander.net>
2012-03-21 17:16 ` Bruce Momjian <bruce@momjian.us>
2012-04-09 18:40 ` Bruce Momjian <bruce@momjian.us>
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