| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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 20:16:24 |
| Message-ID: | 2061855.1680725784@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> 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.
Having two functions doesn't seem unreasonable to me either.
Robert spoke against it to start with, does he still want to
advocate for that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2023-04-05 20:17:20 | Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode |
| Previous Message | Tom Lane | 2023-04-05 20:05:02 | Re: on placeholder entries in view rule action query's range table |