diff options
author | Andres Freund | 2015-08-10 11:28:18 +0000 |
---|---|---|
committer | Andres Freund | 2015-08-10 11:28:18 +0000 |
commit | 3f811c2d6f51b13b71adff99e82894dd48cee055 (patch) | |
tree | d2764ea2b530d2ebed4a16eccaff4e18f6ab5ebf /contrib/test_decoding | |
parent | 5c4b25accebb5d35358bb0c19b841d8d9b064e46 (diff) |
Add confirmed_flush column to pg_replication_slots.
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
Diffstat (limited to 'contrib/test_decoding')
-rw-r--r-- | contrib/test_decoding/expected/ddl.out | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/test_decoding/expected/ddl.out b/contrib/test_decoding/expected/ddl.out index 728798b3b73..11b2d9c07f4 100644 --- a/contrib/test_decoding/expected/ddl.out +++ b/contrib/test_decoding/expected/ddl.out @@ -673,7 +673,7 @@ SELECT pg_drop_replication_slot('regression_slot'); /* check that the slot is gone */ SELECT * FROM pg_replication_slots; - slot_name | plugin | slot_type | datoid | database | active | active_pid | xmin | catalog_xmin | restart_lsn ------------+--------+-----------+--------+----------+--------+------------+------+--------------+------------- + slot_name | plugin | slot_type | datoid | database | active | active_pid | xmin | catalog_xmin | restart_lsn | confirmed_flush_lsn +-----------+--------+-----------+--------+----------+--------+------------+------+--------------+-------------+--------------------- (0 rows) |