Re: shared memory stats ideas

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Lukas Fittl <lukas(at)fittl(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Peter Geoghegan <pg(at)bowt(dot)ie>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: shared memory stats ideas
Date: 2022-10-31 13:20:09
Message-ID: 506d3479-3851-d496-bfa9-64611477a666@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 10/20/22 9:17 AM, Drouvot, Bertrand wrote:
> On 10/19/22 8:19 PM, Andres Freund wrote:
>>
>> 2) Split index and table statistics into different types of stats
>>
>> We track both types of statistics in the same format and rename column in
>> views etc to make them somewhat sensible. A number of the "columns" in
>> index
>> stats are currently unused.
>>
>> If we split the stats for indexes and relations we can have reasonable
>> names
>> for the fields, shrink the current memory usage by halfing the set of
>> fields
>> we keep for indexes, and extend the stats in a more targeted fashion.
>
> I started to work on this.
> I should be able to provide a patch attempt in the next couple of weeks.

Patch submitted and CF entry created:
https://commitfest.postgresql.org/40/3984/

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2022-10-31 13:24:14 Re: Code checks for App Devs, using new options for transaction behavior
Previous Message ilya.v.gladyshev 2022-10-31 13:15:48 Re: Segfault on logical replication to partitioned table with foreign children