diff options
| author | Fujii Masao <fujii@postgresql.org> | 2025-07-03 23:07:23 +0900 |
|---|---|---|
| committer | Fujii Masao <fujii@postgresql.org> | 2025-07-03 23:07:23 +0900 |
| commit | ff3007c66dc6213fcdaea9a996865bbd943e3e82 (patch) | |
| tree | 561aaade08d2c2e124e33fc5f9b8e17797619975 /src/backend/executor/nodeModifyTable.c | |
| parent | 647cffd2f3210818f3882a1ea40cfbe0a4ea8fd7 (diff) | |
| download | postgresql-ff3007c66dc6213fcdaea9a996865bbd943e3e82.tar.gz postgresql-ff3007c66dc6213fcdaea9a996865bbd943e3e82.zip | |
doc: Update outdated descriptions of wal_status in pg_replication_slots.
The documentation for pg_replication_slots previously mentioned only
max_slot_wal_keep_size as a condition under which the wal_status column
could show unreserved or lost. However, since commit be87200,
replication slots can also be invalidated due to horizon or wal_level,
and since commit ac0e33136ab, idle_replication_slot_timeout can also
trigger this state.
This commit updates the description of the wal_status column to
reflect that max_slot_wal_keep_size is not the only cause of the lost state.
Back-patched to v16, where the additional invalidation cases were introduced.
Author: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: Nisha Moond <nisha.moond412@gmail.com>
Discussion: https://postgr.es/m/78b34e84-2195-4f28-a151-5d204a382fdd@oss.nttdata.com
Backpatch-through: 16
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions