Re: monitoring usage count distribution - Mailing list pgsql-hackers

From Tom Lane
Subject Re: monitoring usage count distribution
Date
Msg-id 2061855.1680725784@sss.pgh.pa.us
Whole thread Raw
In response to Re: monitoring usage count distribution  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: monitoring usage count distribution
List pgsql-hackers
Nathan Bossart <nathandbossart@gmail.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: on placeholder entries in view rule action query's range table
Next
From: Melanie Plageman
Date:
Subject: Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode