Re: Handle concurrent drop when doing whole database vacuum - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Handle concurrent drop when doing whole database vacuum
Date
Msg-id akPhEffRipH4isWF@nathan
Whole thread
In response to Re: Handle concurrent drop when doing whole database vacuum  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Jun 30, 2026 at 01:47:41PM +0900, Michael Paquier wrote:
> Something that still feels off to me is to blindly use _ext() in
> vacuum_is_permitted_for_relation(), where we *may* already hold a lock
> on the relation whose ACL is checked.  In this case missing a relation
> is not fine, so this would make the code more brittle in the
> single-relation case under autovacuum or a VACUUM with a list of
> relations provided by a user.

Yeah, so we should only use it for get_all_vacuum_rels(), as in the
attached.

-- 
nathan

Attachment

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: occasional ECPG failures on dikkop (FreeBSD)
Next
From: Corey Huinker
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics