Re: another autovacuum scheduling thread - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: another autovacuum scheduling thread
Date
Msg-id CAMFBP2q-oMzpEua9Hdcpag15VGZn7aEO-uaHZ4yVEO_HCm55_Q@mail.gmail.com
Whole thread
In response to Re: another autovacuum scheduling thread  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: another autovacuum scheduling thread
List pgsql-hackers
On Mon, Mar 23, 2026 at 4:01 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
On Mon, Mar 23, 2026 at 02:01:22PM -0500, Sami Imseih wrote:
> Adding a system view will be nice. I am attaching a version I used in earlier
> testing (cleaned up with docs), if we are inclined to get this in. I
> think it will be
> useful.

Thanks.  IMHO we should continue to focus on the main patch and get that
committed first.

+1 ... for one thing if we're going to add a view meant for monitoring autovac decisions I'd like to think about ways to measure how many tables are "close" to being eligible for autovac. In particular, the scenario where you've just done an MVU via some form of logical, so now the freeze ages on all your tables are extremely similar.

It might be nice if we had an official means of publishing things that we'd really like users to kick the tires on, but hold a clear understanding that we promise no backwards compatibility, promise we'll keep supporting, etc. I can't see how that'd work with backend code, but could certainly be done for anything in userspace.

pgsql-hackers by date:

Previous
From: Steve Chavez
Date:
Subject: [PATCH] refactor ExecCheckPermissionsModified for ACL_SELECT
Next
From: Jim Nasby
Date:
Subject: Re: Add GoAway protocol message for graceful but fast server shutdown/switchover