From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, schneider(at)ardentperf(dot)com |
Subject: | Re: monitoring usage count distribution |
Date: | 2023-04-04 18:40:02 |
Message-ID: | 1586362.1680633602@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Jan 30, 2023 at 6:30 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>> My colleague Jeremy Schneider (CC'd) was recently looking into usage count
>> distributions for various workloads, and he mentioned that it would be nice
>> to have an easy way to do $SUBJECT.
> I'm skeptical that pg_buffercache_summary() is a good idea at all, but
> having it display the average usage count seems like a particularly
> poor idea. That information is almost meaningless. Replacing that with
> a six-element integer array would be a clear improvement and, IMHO,
> better than adding yet another function to the extension.
I had not realized that pg_buffercache_summary() is new in v16,
but since it is, we still have time to rethink its definition.
+1 for de-aggregating --- I agree that the overall average is
unlikely to have much value.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2023-04-04 18:50:53 | Re: proposal: psql: show current user in prompt |
Previous Message | Greg Stark | 2023-04-04 18:36:01 | Re: Commitfest 2023-03 starting tomorrow! |