Re: Vacuum statistics - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Vacuum statistics
Date
Msg-id CAA4eK1JOUn+EqWSfRgKfgBZOXT7Q2dw2enmSZZgOhoMOFwopPA@mail.gmail.com
Whole thread Raw
In response to Re: Vacuum statistics  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Vacuum statistics
List pgsql-hackers
On Fri, May 9, 2025 at 5:34 PM Alena Rybakina <a.rybakina@postgrespro.ru> wrote:
>
> I did a rebase and finished the part with storing statistics separately from the relation statistics - now it is
possibleto disable the collection of statistics for relationsh using gucs and 
> this allows us to solve the problem with the memory consumed.
>

I think this patch is trying to collect data similar to what we do for
pg_stat_statements for SQL statements. So, can't we follow a similar
idea such that these additional statistics will be collected once some
external module like pg_stat_statements is enabled? That module should
be responsible for accumulating and resetting the data, so we won't
have this memory consumption issue.

BTW, how will these new statistics be used to autotune a vacuum? And
do we need all the statistics proposed by this patch?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: libcurl in libpq.pc
Next
From: Peter Geoghegan
Date:
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree