Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit2e619f8

Browse files
committed
Doc: hack on table 26.1 till it fits in PDF format.
I abbreviated the heck out of the column headings, and made a fewsmall wording changes, to get it to build warning-free. I can'tsay that the result is pretty, but it's probably better thanremoving this table entirely.As of this commit, we have zero "exceed the available area" warningsin a US-letter PDF build, and one such warning (about an 863-millipointoverrun) in an A4 build. I expect to get rid of that one by renamingwait events, so I'm not doing anything about it at the formattinglevel.Discussion:https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
1 parent3d14c17 commit2e619f8

File tree

1 file changed

+30
-26
lines changed

1 file changed

+30
-26
lines changed

‎doc/src/sgml/high-availability.sgml

Lines changed: 30 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -198,11 +198,11 @@ protocol to make nodes agree on a serializable transactional order.
198198
</varlistentry>
199199

200200
<varlistentry>
201-
<term>Statement-Based Replication Middleware</term>
201+
<term>SQL-Based Replication Middleware</term>
202202
<listitem>
203203

204204
<para>
205-
Withstatement-based replication middleware, a program intercepts
205+
WithSQL-based replication middleware, a program intercepts
206206
every SQL query and sends it to one or all servers. Each server
207207
operates independently. Read-write queries must be sent to all servers,
208208
so that every server receives any changes. But read-only queries can be
@@ -279,19 +279,6 @@ protocol to make nodes agree on a serializable transactional order.
279279
</listitem>
280280
</varlistentry>
281281

282-
<varlistentry>
283-
<term>Commercial Solutions</term>
284-
<listitem>
285-
286-
<para>
287-
Because <productname>PostgreSQL</productname> is open source and easily
288-
extended, a number of companies have taken <productname>PostgreSQL</productname>
289-
and created commercial closed-source solutions with unique
290-
failover, replication, and load balancing capabilities.
291-
</para>
292-
</listitem>
293-
</varlistentry>
294-
295282
</variablelist>
296283

297284
<para>
@@ -302,36 +289,45 @@ protocol to make nodes agree on a serializable transactional order.
302289
<table id="high-availability-matrix">
303290
<title>High Availability, Load Balancing, and Replication Feature Matrix</title>
304291
<tgroup cols="9">
292+
<colspec colname="col1" colwidth="1.1*"/>
293+
<colspec colname="col2" colwidth="1*"/>
294+
<colspec colname="col3" colwidth="1*"/>
295+
<colspec colname="col4" colwidth="1*"/>
296+
<colspec colname="col5" colwidth="1*"/>
297+
<colspec colname="col6" colwidth="1*"/>
298+
<colspec colname="col7" colwidth="1*"/>
299+
<colspec colname="col8" colwidth="1*"/>
300+
<colspec colname="col9" colwidth="1*"/>
305301
<thead>
306302
<row>
307303
<entry>Feature</entry>
308-
<entry>Shared Disk Failover</entry>
309-
<entry>File SystemReplication</entry>
304+
<entry>Shared Disk</entry>
305+
<entry>File SystemRepl.</entry>
310306
<entry>Write-Ahead Log Shipping</entry>
311-
<entry>LogicalReplication</entry>
312-
<entry>Trigger-BasedMaster-Standby Replication</entry>
313-
<entry>Statement-Based Replication Middleware</entry>
314-
<entry>Asynchronous Multimaster Replication</entry>
315-
<entry>Synchronous Multimaster Replication</entry>
307+
<entry>LogicalRepl.</entry>
308+
<entry>Trigger-BasedRepl.</entry>
309+
<entry>SQL Repl. Middle-ware</entry>
310+
<entry>Async. MM Repl.</entry>
311+
<entry>Sync. MM Repl.</entry>
316312
</row>
317313
</thead>
318314

319315
<tbody>
320316

321317
<row>
322-
<entry>Most common implementations</entry>
318+
<entry>Popular examples</entry>
323319
<entry align="center">NAS</entry>
324320
<entry align="center">DRBD</entry>
325-
<entry align="center">built-in streamingreplication</entry>
326-
<entry align="center">built-in logicalreplication, pglogical</entry>
321+
<entry align="center">built-in streamingrepl.</entry>
322+
<entry align="center">built-in logicalrepl., pglogical</entry>
327323
<entry align="center">Londiste, Slony</entry>
328324
<entry align="center">pgpool-II</entry>
329325
<entry align="center">Bucardo</entry>
330326
<entry align="center"></entry>
331327
</row>
332328

333329
<row>
334-
<entry>Communication method</entry>
330+
<entry>Comm. method</entry>
335331
<entry align="center">shared disk</entry>
336332
<entry align="center">disk blocks</entry>
337333
<entry align="center">WAL</entry>
@@ -485,6 +481,14 @@ protocol to make nodes agree on a serializable transactional order.
485481

486482
</variablelist>
487483

484+
<para>
485+
It should also be noted that because <productname>PostgreSQL</productname>
486+
is open source and easily extended, a number of companies have
487+
taken <productname>PostgreSQL</productname> and created commercial
488+
closed-source solutions with unique failover, replication, and load
489+
balancing capabilities. These are not discussed here.
490+
</para>
491+
488492
</sect1>
489493

490494

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp