|
|
|
|
@ -486,7 +486,7 @@ protocol to make nodes agree on a serializable transactional order. |
|
|
|
|
<para> |
|
|
|
|
Directly moving WAL records from one database server to another |
|
|
|
|
is typically described as log shipping. <productname>PostgreSQL</> |
|
|
|
|
implements file-based log shipping by transfering WAL records |
|
|
|
|
implements file-based log shipping by transferring WAL records |
|
|
|
|
one file (WAL segment) at a time. WAL files (16MB) can be |
|
|
|
|
shipped easily and cheaply over any distance, whether it be to an |
|
|
|
|
adjacent system, another system at the same site, or another system on |
|
|
|
|
@ -944,7 +944,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
After a commit record has been written to disk on the primary the |
|
|
|
|
After a commit record has been written to disk on the primary, the |
|
|
|
|
WAL record is then sent to the standby. The standby sends reply |
|
|
|
|
messages each time a new batch of WAL data is written to disk, unless |
|
|
|
|
<varname>wal_receiver_status_interval</> is set to zero on the standby. |
|
|
|
|
|