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>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, schneider(at)ardentperf(dot)com |
Subject: | Re: monitoring usage count distribution |
Date: | 2023-04-05 19:07:10 |
Message-ID: | 2020452.1680721630@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 Wed, Apr 5, 2023 at 1:51 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>> The six-element array approach won't show the number of dirty and pinned
>> buffers for each usage count, but I'm not sure that's a deal-breaker.
>> Barring objections, I'll post an updated patch shortly with that approach.
> Right, well, I would personally be OK with 6 rows too, but I don't
> know what other people want. I think either this or that is better
> than average.
Seems to me that six rows would be easier to aggregate manually.
An array column seems less SQL-ish and harder to manipulate.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-04-05 19:09:21 | Re: monitoring usage count distribution |
Previous Message | Daniel Gustafsson | 2023-04-05 19:03:53 | Re: Should vacuum process config file reload more often |