Re: Auto Vacuum optimisation - Mailing list pgsql-hackers

From Japin Li
Subject Re: Auto Vacuum optimisation
Date
Msg-id ME0P300MB0445EBD1D3DAE6066C639813B62F2@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM
Whole thread Raw
List pgsql-hackers
On Mon, 18 Nov 2024 at 18:20, wenhui qiu <qiuwenhuifx@gmail.com> wrote:
> HI hackers
>    These are algorithmic mathematical graphs,By default, vacuum will not be triggered frequently.Looking at the
images
> the algorithms for pow and sqrt are close, do we want to cancel one of the algorithms? 
>
> log2 
> image.png
>
> sqrt
> image.png
> pow
> image.png
>

Sorry for the late reply.

Did you forget to upload the pictures?

>        There was an earlier discussion about auto vacuum optimisation(
>  https://www.postgresql.org/message-id/6a2ac9b7-6535-4bb1-8274-0647f7c31c82%40dalibo.com),I referring to the
>  discussion in there, I implemented a parameter selection triggering the calculation of AUTO VACUUM,This is my first
>  patch for the community.Hoping for support from the experts

I think this is helpful.

One of our customers had large tables that were frequently updated, and their
global configuration did not permit timely VACUUM operations on those tables.
As a result, they had to adjust the vacuum settings for those specific tables,
which unintentionally increased their maintenance burden.

However, I'm not sure we need so many autovacuum algorithms here since it makes
the choice harder (maybe).

-- 
Regrads,
Japin Li



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Potential Issue with Redundant Restriction Clauses in get_parameterized_baserel_size for PARTITIONED_REL
Next
From: Jim Jones
Date:
Subject: Re: PoC: Simplify recovery after dropping a table by LOGGING the restore LSN