Add confirmed_flush column to pg_replication_slots

Enterprise / PostgreSQL - Andres Freund [anarazel.de] - 10 August 2015 06:28 UTC

There's no reason not to expose both restart_lsn and confirmed_flush since they have rather distinct meanings. The former is the oldest WAL still required and valid for both physical and logical slots, whereas the latter is the location up to which a logical slot's consumer has confirmed receiving data. Most of the time a slot will require older WAL (i.e. restart_lsn) than the confirmed position (i.e. confirmed_flush_lsn).

Author: Marko Tiikkaja, editorialized by me Discussion: 559D110B.1020109@joh.to

3f811c2 Add confirmed_flush column to pg_replication_slots.
contrib/test_decoding/expected/ddl.out | 4 ++--
doc/src/sgml/catalogs.sgml | 11 +++++++++++
doc/src/sgml/high-availability.sgml | 6 +++---
doc/src/sgml/logicaldecoding.sgml | 8 ++++----
src/backend/catalog/system_views.sql | 3 ++-
src/backend/replication/slotfuncs.c | 9 ++++++++-
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.h | 2 +-
src/test/regress/expected/rules.out | 5 +++--
9 files changed, 35 insertions(+), 15 deletions(-)

Upstream: git.postgresql.org

  • Share