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:09:14 +0900 |
| commit | ba9201b57b00b8f9a612a3fd1ae22a768556cb3d (patch) | |
| tree | 9cfe03899d9491773f0fd71d11fd5fb7bc7110d0 /src | |
| parent | 27224e660aca7704e565ff6d7fc1c8f262c2f05c (diff) | |
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')
0 files changed, 0 insertions, 0 deletions