| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Design of pg_stat_subscription_workers vs pgstats |
| Date: | 2022-02-24 09:48:41 |
| Message-ID: | c62e518d-29e5-0271-1b22-1870bc90ff55@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-02-24 09:53:02 | Re: Design of pg_stat_subscription_workers vs pgstats |
| Previous Message | Aleksander Alekseev | 2022-02-24 09:47:36 | Re: Extract epoch from Interval weird behavior |