Re: min_safe_lsn column in pg_replication_slots view - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: min_safe_lsn column in pg_replication_slots view
Date
Msg-id 20200701151421.GA8125@alvherre.pgsql
Whole thread Raw
In response to Re: min_safe_lsn column in pg_replication_slots view  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: min_safe_lsn column in pg_replication_slots view  (michael@paquier.xyz)
Re: min_safe_lsn column in pg_replication_slots view  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2020-Jul-01, Amit Kapila wrote:

> Okay, but do we think it is better to display this in
> pg_replication_slots or some new view like pg_stat_*_slots as being
> discussed in [1]?  It should not happen that we later decide to move
> this or similar stats to that view.

It seems that the main motivation for having some counters in another
view is the ability to reset them; and resetting this distance value
makes no sense, so I think it's better to have it in
pg_replication_slots.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Collation versioning
Next
From: "Zidenberg, Tsahi"
Date:
Subject: [PATCH] audo-detect and use -moutline-atomics compilation flag for aarch64