From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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-05 13:44:58 |
Message-ID: | CA+TgmobrQ90KGN4dwxL8q-LV529gCMmzXiy8CG5eQwjYTPzZLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 4, 2023 at 7:29 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I'm skeptical that pg_buffercache_summary() is a good idea at all
>
> Why? It's about two orders of magnitude faster than querying the equivalent
> data by aggregating in SQL. And knowing how many free and dirty buffers are
> over time is something quite useful to monitor / correlate with performance
> issues.
Well, OK, fair point.
> > but having it display the average usage count seems like a particularly poor
> > idea. That information is almost meaningless.
>
> I agree there are more meaningful ways to represent the data, but I don't
> agree that it's almost meaningless. It can give you a rough estimate of
> whether data in s_b is referenced or not.
I might have overstated my case.
> > 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'd have no issue with that.
Cool.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-04-05 13:56:35 | Re: proposal: psql: show current user in prompt |
Previous Message | Robert Haas | 2023-04-05 13:28:36 | Re: proposal: psql: show current user in prompt |