Re: Design of pg_stat_subscription_workers vs pgstats
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>, Amit Kapila <amit.kapila16@gmail.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>,
"David G. Johnston" <david.g.johnston@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-02-24T09:20:39Z
Lists: pgsql-hackers
On 21.02.22 17:17, Andres Freund wrote: > Hi, > > On 2022-02-21 14:49:01 +0530, Amit Kapila wrote: >> On Mon, Feb 21, 2022 at 1:18 PM Andres Freund <andres@anarazel.de> wrote: >>>> * stats_reset (Time at which these statistics were last reset) >>>> >>>> The view name could be pg_stat_subscription_lrep, >>>> pg_stat_logical_replication, or something on those lines. >>> >>> pg_stat_subscription_stats :) > >> Having *stat* two times in the name sounds slightly odd to me but let >> us see what others think. One more option could be >> pg_stat_subscription_replication. > > It was a joke, making light of our bad naming in pg_stat_*, not a serious > suggestion... I think pg_stat_subscription_stats is actually the least worst option. Unless we want to consider renaming pg_stat_subscription (which is actually more like pg_stat_subscription_activity). But I think that should be avoided.
Commits
-
Reconsider pg_stat_subscription_workers view.
- 7a8507329085 15.0 landed
-
Add a view to show the stats of subscription workers.
- 8d74fc96db5f 15.0 cited