diff options
| author | Amit Kapila <akapila@postgresql.org> | 2024-03-25 16:34:33 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2024-03-25 16:34:33 +0530 |
| commit | a11f330b5584f2430371d68871e00f5c63735299 (patch) | |
| tree | b53cafab5f97bb5440db906e20ca0f38e46a0fd9 /src/backend/access/gist/gistxlog.c | |
| parent | 0f7863afef67e462574fe5af6317e26a2f2d47fb (diff) | |
| download | postgresql-a11f330b5584f2430371d68871e00f5c63735299.tar.gz postgresql-a11f330b5584f2430371d68871e00f5c63735299.zip | |
Track last_inactive_time in pg_replication_slots.
This commit adds a new property called last_inactive_time for slots. It is
set to 0 whenever a slot is made active/acquired and set to the current
timestamp whenever the slot is inactive/released or restored from the disk.
Note that we don't set the last_inactive_time for the slots currently being
synced from the primary to the standby because such slots are typically
inactive as decoding is not allowed on those.
The 'last_inactive_time' will be useful on production servers to debug and
analyze inactive replication slots. It will also help to know the lifetime
of a replication slot - one can know how long a streaming standby, logical
subscriber, or replication slot consumer is down.
The 'last_inactive_time' will also be useful to implement inactive
timeout-based replication slot invalidation in a future commit.
Author: Bharath Rupireddy
Reviewed-by: Bertrand Drouvot, Amit Kapila, Shveta Malik
Discussion: https://www.postgresql.org/message-id/CALj2ACW4aUe-_uFQOjdWCEN-xXoLGhmvRFnL8SNw_TZ5nJe+aw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions