Re: Disabling vacuum truncate for autovacuum - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Disabling vacuum truncate for autovacuum
Date
Msg-id 97160e4b549c726bd409c8059a1bfaf07e7a6d04.camel@cybertec.at
Whole thread Raw
In response to Re: Disabling vacuum truncate for autovacuum  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Thu, 2025-02-27 at 21:35 -0600, Nathan Bossart wrote:
> I spent some time on this one today.  A couple of notes:
>
> * Since the reloption is a Boolean, there isn't a good way to tell whether
>   it is actually set for the table or if it just inherited the default
>   value.  This is important to know because we want the reloption to
>   override the GUC.

I agree with that, without being able to think of a better solution.

> * I didn't see a good GUC category for vacuum_truncate.  I suppose we could
>   create a new one, but for now I've just stashed it into the autovacuum
>   one.  Bikeshedding welcome.

Why not use "Client Connection Defaults / Statement Behavior", just like for
"vacuum_freeze_min_age"?  I don't think that "autovacuum" is appropriate,
since it applies to manual VACUUM as well.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Sagar Shedge
Date:
Subject: Re: Extend postgres_fdw_get_connections to return remote backend pid
Next
From: Abhishek Chanda
Date:
Subject: Re: Adding support for SSLKEYLOGFILE in the frontend