Re: New GUC autovacuum_max_threshold ? - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: New GUC autovacuum_max_threshold ?
Date
Msg-id CAA5RZ0sV87qg08JzzdfcZc7Qdfr=Rh0gxq_Bo+AQ_hQgARUjyg@mail.gmail.com
Whole thread Raw
In response to Re: New GUC autovacuum_max_threshold ?  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: New GUC autovacuum_max_threshold ?
List pgsql-hackers
On Tue, Jan 14, 2025 at 11:45 AM Nathan Bossart
<nathandbossart@gmail.com> wrote:
>
> On Tue, Jan 14, 2025 at 11:08:36AM -0600, Sami Imseih wrote:
> > After staring at the documentation for a while, I am now
> > wondering whether we are adequately describing the
> > rationale for this GUC. The GUC documentation mentions that this is a
> > 'cap on the value calculated with autovacuum_vacuum_threshold
> > and autovacuum_vacuum_scale_factor,' which is acceptable;
> > however, I think further elaboration is necessary in
> > routine-vacuuming.html#AUTOVACUUM. This is because
> > scale_factor and threshold are already well-known
> > and widely understood parameters, and introducing
> > a third one to the mix deserves a bit more of an
> > explanation. What do you think?
>
> I think it would be odd to explain the intent for one autovacuum parameter
> while leaving the others unexplained.  IMHO it would be better to address
> this for all such parameters in a follow-up patch.

absolutely, the documentation will need to discuss the relationship
between all 3 parameters for the documentation to make sense.

Regards,

Sami



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: New GUC autovacuum_max_threshold ?
Next
From: Alvaro Herrera
Date:
Subject: Re: Reduce TupleHashEntryData struct size by half