Re: shared-memory based stats collector - v70

From: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: shared-memory based stats collector - v70
Date: 2022-08-09 10:18:47
Message-ID: caa515eb-e9e7-9fe7-ceb1-a96b6f3787ce@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 7/21/22 5:07 PM, Greg Stark wrote:
> On Wed, 20 Jul 2022 at 15:09, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> What are your trying to do?
> Ideally I would want to dump out the stats without connecting to each
> database.

I can see the use case too (specially for monitoring tools) of being
able to collect the stats without connecting to each database.

> It seems like just having an interface to iterate over the shared hash
> table and return entries one by one without filtering by database
> would be fairly straightforward and I would be able to do most of what
> I want just with that.

What do you think about adding a function in core PG to provide such
functionality? (means being able to retrieve all the stats (+ eventually
add some filtering) without the need to connect to each database).

If there is some interest, I'd be happy to work on it and propose a patch.

Regards,

--
Bertrand Drouvot
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message r.zharkov 2022-08-09 10:29:00 Re: Checking pgwin32_is_junction() errors
Previous Message Álvaro Herrera 2022-08-09 09:48:23 Re: support for MERGE