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

From Kyotaro Horiguchi
Subject Re: Handle concurrent drop when doing whole database vacuum
Date
Msg-id 20260702.150349.672440168192810994.horikyota.ntt@gmail.com
Whole thread
In response to Re: Handle concurrent drop when doing whole database vacuum  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hello,

At Wed, 1 Jul 2026 08:35:12 +0900, Michael Paquier <michael@paquier.xyz> wrote in 
> > 3. The Assert that Bharath suggested earlier doesn't apply as-is but can be
> > incorporated into the patch as:
> > Assert(missing_ok || CheckRelationOidLockedByMe(relid, AccessShareLock,
> > true));
> 
> This fail-safe would be a welcome addition, yes.  Perhaps Nathan feels
> differently, which would be also fine by me.

To me, this Assert seems worthwhile as part of the function's contract.

Regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Ewan Young
Date:
Subject: Re: Fix jsonpath .decimal() to honor silent mode
Next
From: solai v
Date:
Subject: Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values