Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
Date: 2026-10-07 19:04:38
Message-ID: CAD21AoC=pqo5oQGLD--7pedB6yRO-Q63W=BLCPhc3m8TeXrjcA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 6, 2026 at 9:00 PM shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> Hi Sawada-san,
>
> Attached v5 drops the lock and adds a comment on why the read is safe.
> It also adds the !OidIsValid(leader->roleId) check and sets roleId to
> InvalidOid directly, so only a leader with no advertised role changes
> anything.

Thank you for updating the patch. Could you also share your thoughts
on the points I raised in my previous email?

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-07 19:07:27 Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Previous Message Nathan Bossart 2026-10-07 18:55:59 Re: LWLock granular partition lock memory layout