↑↓ select↵ open⌫ change scopeOpen full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Configuration Parameters

synchronized_standby_slots

A comma-separated list of streaming replication standby server slot names that logical WAL sender processes will wait for. Logical WAL sender processes will send decoded changes to plugins only after the specified replication slots confirm receiving WAL. This guarantees that logical replication failover slots do not consume changes until those changes are received and flushed to corresponding physical standbys. If a logical replication connection is meant to switch to a physical standby after the standby is promoted, the physical replication slot for the standby should be listed here. Note that logical replication will not proceed if the slots specified in the synchronized_standby_slots do not exist or are invalidated. Additionally, the replication management functions pg_replication_slot_advance, pg_logical_slot_get_changes, and pg_logical_slot_peek_changes, when used with logical failover slots, will block until all physical slots specified in synchronized_standby_slots have confirmed WAL receipt. The standbys corresponding to the physical replication slots in synchronized_standby_slots must configure sync_replication_slots = true so they can receive logical failover slot changes from the primary.

English manual coverage begins with PostgreSQL 7.4. Source history and runtime observations have their own recorded version boundaries.

Reading PG 18·Select a recorded version

boot val
Unknown
category
Replication / Primary Server
context
sighup
doc same as
Unknown
documented
true
enumvals
Unknown
extra desc
Logical WAL sender processes will send decoded changes to output plugins only after the specified replication slots have confirmed receiving WAL.
lang
en
max val
Unknown
metadata version
18
min val
Unknown
name
synchronized_standby_slots
short desc
Lists streaming replication standby server replication slot names that logical WAL sender processes will wait for.
source
pg-settings-source-snapshot
unit
Unknown
vartype
string

Definition PG 18

A comma-separated list of streaming replication standby server slot names that logical WAL sender processes will wait for. Logical WAL sender processes will send decoded changes to plugins only after the specified replication slots confirm receiving WAL. This guarantees that logical replication failover slots do not consume changes until those changes are received and flushed to corresponding physical standbys. If a logical replication connection is meant to switch to a physical standby after the standby is promoted, the physical replication slot for the standby should be listed here. Note that logical replication will not proceed if the slots specified in the synchronized_standby_slots do not exist or are invalidated. Additionally, the replication management functions pg_replication_slot_advance, pg_logical_slot_get_changes, and pg_logical_slot_peek_changes, when used with logical failover slots, will block until all physical slots specified in synchronized_standby_slots have confirmed WAL receipt.

The standbys corresponding to the physical replication slots in synchronized_standby_slots must configure sync_replication_slots = true so they can receive logical failover slot changes from the primary.

Compare versions

Complete source facts

doc html

<p>
        A comma-separated list of streaming replication standby server slot names
        that logical WAL sender processes will wait for. Logical WAL sender processes
        will send decoded changes to plugins only after the specified replication
        slots confirm receiving WAL. This guarantees that logical replication
        failover slots do not consume changes until those changes are received
        and flushed to corresponding physical standbys. If a
        logical replication connection is meant to switch to a physical standby
        after the standby is promoted, the physical replication slot for the
        standby should be listed here. Note that logical replication will not
        proceed if the slots specified in the
        <code class="varname">synchronized_standby_slots</code> do not exist or are invalidated.
        Additionally, the replication management functions
        <a class="link" href="/docs/18/functions-admin.html#PG-REPLICATION-SLOT-ADVANCE">
<code class="function">pg_replication_slot_advance</code></a>,
        <a class="link" href="/docs/18/functions-admin.html#PG-LOGICAL-SLOT-GET-CHANGES">
<code class="function">pg_logical_slot_get_changes</code></a>, and
        <a class="link" href="/docs/18/functions-admin.html#PG-LOGICAL-SLOT-PEEK-CHANGES">
<code class="function">pg_logical_slot_peek_changes</code></a>,
        when used with logical failover slots, will block until all
        physical slots specified in <code class="varname">synchronized_standby_slots</code> have
        confirmed WAL receipt.
       </p><p>
        The standbys corresponding to the physical replication slots in
        <code class="varname">synchronized_standby_slots</code> must configure
        <code class="literal">sync_replication_slots = true</code> so they can receive
        logical failover slot changes from the primary.
       </p>

documentation revision

{"inputs":[{"file":"runtime-config-replication.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"c0b8bd86131ec62d4df97ce480d004aa7e3544477d053f0c2d4047b9edad5cc0","version":"18.7"},{"file":"runtime-config-replication.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"83907b5f469e979a7b9ec875b5e7bdaa2ef6b85596ca31b45174f68cd7398b18","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}

Source references

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · wiki-repair-20261023:0acc01a74bc7c525643b2a1bab5ecde8031a77334e75ed9155e38b4d60a43193

Text language: en · wiki-repair-20261023:0acc01a74bc7c525643b2a1bab5ecde8031a77334e75ed9155e38b4d60a43193