Re: Disabling vacuum truncate for autovacuum

From: Will Storey <will(at)summercat(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Disabling vacuum truncate for autovacuum
Date: 2024-12-17 18:03:44
Message-ID: Z2G9ANcb8oU81shW@dev.null
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2024-12-17 18:39:11 Re: Credcheck- credcheck.max_auth_failure
Previous Message Enrico Schenone 2024-12-17 16:30:16 Intermittent errors when fetching cursor rows on PostgreSQL 16