sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

Minor improvements to replication slot documentation.

Browse Source 
Fix a thinko pointed out by Jeff Davis, and convert a couple of other
references into links.
This commit is contained in:
Robert Haas 2014-02-05 13:41:25 -05:00
parent 4e18236180
commit 14aa601f50
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/high-availability.sgml
View File

@ -889,7 +889,8 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
<para>
In lieu of using replication slots, it is possible to prevent the removal
of old WAL segments using <xref linkend="guc-wal-keep-segments">, or by
storing the segments in an archive using <xref linkend="restore-command">.
storing the segments in an archive using
<xref linkend="guc-archive-command">.
However, these methods often result in retaining more WAL segments than
required, whereas replication slots retain only the number of segments
known to be needed. An advantage of these methods is that they bound
@ -897,8 +898,8 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
to do this using replication slots.
</para>
<para>
Similarly, <varname>hot_standby_feedback</varname>
and <varname>vacuum_defer_cleanup_age</varname> provide protection against
Similarly, <xref linkend="guc-hot-standby-feedback">
and <xref linkend="guc-vacuum-defer-cleanup-age"> provide protection against
relevant rows being removed by vacuum, but the former provides no
protection during any time period when the standby is not connected,
and the latter often needs to be set to a high value to provide adequate