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>,
Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
"David G. Johnston" <david.g.johnston@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-02-24T09:48:41Z
Lists: pgsql-hackers
On 23.02.22 03:14, Andres Freund wrote: > Why are the stats stored in the per-database stats file / as a second level > below the database? While they're also associated with a database, it's a > global catalog, so it seems to make more sense to have them "live" globally as > well? pg_subscription being a global catalog is a bit of a lie for the benefit of the worker launcher, but it can be treated as a per-database catalog for practical purposes. > Not just from an aesthetical perspective, but there might also be cases where > it's useful to send stats from the stats launcher. E.g. the number of times > the launcher couldn't start a worker because the max numbers of workers was > already active or such. That's a reasonable point, however.
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