]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Morph pg_replication_slots.min_safe_lsn to safe_wal_size
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 7 Jul 2020 17:08:00 +0000 (13:08 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 7 Jul 2020 17:08:00 +0000 (13:08 -0400)
commitc54b5891f415df36809de1aeb97e4574d5456d69
tree54c89c84b8ae4651bb9ba66254114ca8aa02b997
parentda6b6ff95bcaadc109ab248471527a2511e853d5
Morph pg_replication_slots.min_safe_lsn to safe_wal_size

The previous definition of the column was almost universally disliked,
so provide this updated definition which is more useful for monitoring
purposes: a large positive value is good, while zero or a negative value
means danger.  This should be operationally more convenient.

Backpatch to 13, where the new column to pg_replication_slots (and the
feature it represents) were added.

Author: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Reported-by: Fujii Masao <masao.fujii@oss.nttdata.com>
Discussion: https://postgr.es/m/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com
doc/src/sgml/catalogs.sgml
src/backend/access/transam/xlog.c
src/backend/catalog/system_views.sql
src/backend/replication/slotfuncs.c
src/include/access/xlog_internal.h
src/include/catalog/catversion.h
src/include/catalog/pg_proc.dat
src/test/recovery/t/019_replslot_limit.pl
src/test/regress/expected/rules.out