agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: cca5507 <cca5507@qq.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Cc: Jeff Davis <pgsql@j-davis.com>
Subject: Re: Handle concurrent drop when doing whole database vacuum
Date: Mon, 29 Jun 2026 11:54:44 -0500
Message-ID: <akKjVNL9LyTexpEi@nathan> (raw)
In-Reply-To: <ajsZZlgYYPa37CIz@paquier.xyz>
References: <tencent_F9D483523BB0D082C2EFDA80142F192DBC07@qq.com>
<20260615.145410.2255263073807327959.horikyota.ntt@gmail.com>
<tencent_E642C6000FE760D72E2BD4AD30BC562E2505@qq.com>
<ajsTKldYusgjIzKI@paquier.xyz>
<CALj2ACV8NWt0AtBd35km0YTCu7+forTjpDm09V3HWJRfGAMhoA@mail.gmail.com>
<ajsZZlgYYPa37CIz@paquier.xyz>
On Wed, Jun 24, 2026 at 08:40:22AM +0900, Michael Paquier wrote:
> I'd sure welcome Nathan and Jeff opinions (added now in CC) regarding
> this line of thoughts; they worked on MAINTAIN, even if the early
> relation ACL check when building a list of relations for a
> database-wide manual VACUUM predates that.
I'm mostly concerned about reopening the ability for folks to take strong
locks on catalogs without the necessary privileges, even if they are only
briefly held. Commit a556549 fixed a real problem, so I'm nervous about
partially reverting it. IOW my first reaction is that v1 is the right
idea, i.e., we should just skip the relation if it disappears. I'm not
sure we even need to log it.
--
nathan
view thread (44+ messages) latest in thread
Message-ID: <akKjVNL9LyTexpEi@nathan>
Permalink: ../akKjVNL9LyTexpEi@nathan/
Also on: postgresql.org/message-id/akKjVNL9LyTexpEi@nathan
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nathandbossart@gmail.com, michael@paquier.xyz, bharath.rupireddyforpostgres@gmail.com, cca5507@qq.com, horikyota.ntt@gmail.com, pgsql-hackers@lists.postgresql.org, pgsql@j-davis.com
Subject: Re: Handle concurrent drop when doing whole database vacuum
In-Reply-To: <akKjVNL9LyTexpEi@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox