Request a Demo
Home   >   mailing lists

Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
Date
Msg-id CAD21AoC=pqo5oQGLD--7pedB6yRO-Q63W=BLCPhc3m8TeXrjcA@mail.gmail.com
Whole thread
In response to Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers  (shihao zhong <zhong950419@gmail.com>)
Responses Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
List pgsql-hackers
Tree view 
On Tue, Oct 6, 2026 at 9:00 PM shihao zhong <zhong950419@gmail.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

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: LWLock granular partition lock memory layout
Next
From: Masahiko Sawada
Date:
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation