database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-18 02:02:55 +03:00
Code Activity

doc: adjust "Replication Slot" to mention physical & logical

Browse Source 
Much of the "Replication Slot" chapter applies to physical and logical
slots, but it was sloppy in mentioning mostly physical slots.  This
patch clarified which parts of the text apply to which slot types.

This chapter is referenced from the logical slot/subscriber chapter, so
it needs to do double duty.

Backpatch-through: master
This commit is contained in:
Bruce Momjian
2025-11-13 21:53:13 -05:00
parent ada78cd7f8
commit 8fa6b9030d
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -918,18 +918,18 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
</sect2> </sect2>
<sect2 id="streaming-replication-slots"> <sect2 id="streaming-replication-slots">
<title>Physical Replication Slots</title> <title>Replication Slots</title>
<indexterm> <indexterm>
<primary>replication slot</primary> <primary>replication slot</primary>
<secondary>streaming replication</secondary> <secondary>streaming replication</secondary>
</indexterm> </indexterm>
<para> <para>
Physical replication slots provide an automated way to ensure that the Replication slots provide an automated way to ensure that the
primary server does primary server does not remove WAL segments until they have been
not remove WAL segments until they have been received by all standbys, received, physically or logically, by all standbys/subscribers,
and that the primary does not remove rows which could cause a and that the primary does not remove rows which could cause a <link
<link linkend="hot-standby-conflict">recovery conflict</link> even when the linkend="hot-standby-conflict">recovery conflict</link> on physical
standby is disconnected. replicas even when the standby is disconnected.
</para> </para>
<para> <para>
In lieu of using replication slots, it is possible to prevent the removal In lieu of using replication slots, it is possible to prevent the removal
@@ -943,9 +943,9 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
</para> </para>
<para> <para>
Similarly, <xref linkend="guc-hot-standby-feedback"/> on its own, without Similarly, <xref linkend="guc-hot-standby-feedback"/> on its own, without
also using a replication slot, provides protection against relevant rows also using a physical replication slot, provides protection against relevant rows
being removed by vacuum, but provides no protection during any time period being removed by vacuum, but provides no protection during any time period
when the standby is not connected. when the physical replication standby is disconnected.
</para> </para>
<caution> <caution>