Sender: Will Storey <wstorey@gmail.com>
Date: Tue, 17 Dec 2024 10:03:44 -0800
From: Will Storey <will@summercat.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Disabling vacuum truncate for autovacuum
Message-ID: <Z2G9ANcb8oU81shW@dev.null>
References: <Z2DE4lDX4tHqNGZt@dev.null>
 <fa83a77bbca5da4d4864a49c8a27df323f23d28b.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <fa83a77bbca5da4d4864a49c8a27df323f23d28b.camel@cybertec.at>
Archived-At: <https://www.postgresql.org/message-id/Z2G9ANcb8oU81shW%40dev.null>
Precedence: bulk

On Tue 2024-12-17 08:30:19 +0100, Laurenz Albe wrote:
> > Would I need to disable the settings on catalog tables too? (To rule out
> > any possibility of it happening). Are there any other things I might be
> > missing?
> 
> Potentially yes.  But unless you are using temporary tables or create,
> alter and drop lots of objects, that shouldn't be necessary.

I see. That makes sense. I do have some things that use temporary tables as
well as some jobs that create/drop objects. They are not very frequent nor
are there a huge number objects involved, but I suppose it could still be
an issue. I'm not keen on altering the catalogs, but it sounds like if I
want to be very safe then I would need to.

> > I am also wondering if having an autovacuum setting to control it would be
> > a good idea for a feature.
> 
> I'm all for that.

I previously had old_snapshot_threshold enabled, which would have done this
anyway I believe, including for the catalog tables. That was convenient!

> Yours,
> Laurenz Albe

Thank you Laurenz! I've read a bunch of your writing and I've learned a lot
from you. I'm a big fan :-). Thank you for what you do!