diff options
| author | Amit Kapila | 2024-07-01 06:06:56 +0000 |
|---|---|---|
| committer | Amit Kapila | 2024-07-01 06:06:56 +0000 |
| commit | 2357c9223b710c91b0f05cbc56bd435baeac961f (patch) | |
| tree | aa6c7bd96ebff42cab21978962dede203e82b61e /doc/src/sgml/logicaldecoding.sgml | |
| parent | 0c3930d0768943ad1dedb5a6ace250ce9b65915c (diff) | |
Rename standby_slot_names to synchronized_standby_slots.
The standby_slot_names GUC allows the specification of physical standby
slots that must be synchronized before the logical walsenders associated
with logical failover slots. However, for this purpose, the GUC name is
too generic.
Author: Hou Zhijie
Reviewed-by: Bertrand Drouvot, Masahiko Sawada
Backpatch-through: 17
Discussion: https://postgr.es/m/ZnWeUgdHong93fQN@momjian.us
Diffstat (limited to 'doc/src/sgml/logicaldecoding.sgml')
| -rw-r--r-- | doc/src/sgml/logicaldecoding.sgml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 5a15bbc580c..1c4ae38f1b9 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -385,16 +385,16 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU <literal>dbname</literal> in the <link linkend="guc-primary-conninfo"><varname>primary_conninfo</varname></link>. It's highly recommended that the said physical replication slot is named in - <link linkend="guc-standby-slot-names"><varname>standby_slot_names</varname></link> + <link linkend="guc-synchronized-standby-slots"><varname>synchronized_standby_slots</varname></link> list on the primary, to prevent the subscriber from consuming changes faster than the hot standby. Even when correctly configured, some latency is expected when sending changes to logical subscribers due to the waiting on slots named in - <link linkend="guc-standby-slot-names"><varname>standby_slot_names</varname></link>. - When <varname>standby_slot_names</varname> is utilized, the + <link linkend="guc-synchronized-standby-slots"><varname>synchronized_standby_slots</varname></link>. + When <varname>synchronized_standby_slots</varname> is utilized, the primary server will not completely shut down until the corresponding standbys, associated with the physical replication slots specified - in <varname>standby_slot_names</varname>, have confirmed + in <varname>synchronized_standby_slots</varname>, have confirmed receiving the WAL up to the latest flushed position on the primary server. </para> |