| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, schneider(at)ardentperf(dot)com |
| Subject: | Re: monitoring usage count distribution |
| Date: | 2023-04-05 19:41:01 |
| Message-ID: | 20230405194101.GB105962@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 05, 2023 at 12:09:21PM -0700, Andres Freund wrote:
> I would not mind having a separate function returning 6 rows, if we really
> want that, but making pg_buffercache_summary() return 6 rows would imo make it
> less useful for getting a quick overview. At least I am not that quick summing
> up multple rows, just to get a quick overview over the number of dirty rows.
This is what v1-0001 does. We could probably make pg_buffercache_summary a
view on pg_buffercache_usage_counts, too, but that doesn't strike me as
tremendously important.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-04-05 19:42:33 | Re: Should vacuum process config file reload more often |
| Previous Message | Nathan Bossart | 2023-04-05 19:35:05 | Re: monitoring usage count distribution |