Re: Split index and table statistics into different types of stats

From: Andres Freund <andres(at)anarazel(dot)de>
To: Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>
Cc: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Split index and table statistics into different types of stats
Date: 2023-01-09 20:04:57
Message-ID: 20230109200457.iuynr4fjkc3w4dsd@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2023-01-09 17:08:42 +0530, Nitin Jadhav wrote:
> +1 to keep common functions/code between table and index stats. Only
> the data structure should be different as the goal is to shrink the
> current memory usage.

I don't think the goal is solely to shrink memory usage - it's also to make it
possible to add more stats that are specific to just indexes or just
tables. Of course that's related to memory usage...

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-01-09 20:08:30 pgsql: Doc: add XML ID attributes to <sectN> and <varlistentry> tags.
Previous Message Peter Geoghegan 2023-01-09 20:04:15 Re: Fixing a couple of buglets in how VACUUM sets visibility map bits