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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: 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-15 02:14:15
Message-ID: CALj2ACWhiPG34areeziJHiGxCqfeo-ibtageK0SMt4qe2sboOg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Oct 14, 2026 at 12:03 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> I think that distinction is not visible to users. A parallel worker
> always connects to the same database as its leader, so the leader is
> checked too, with the same role.

Since the code comments already specify that, I think it is fine not
to have anything in the docs. So I removed the doc changes and
addressed the other comments as well. Please find the attached v4
patches.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v4-0001-Fix-DROP-DATABASE-FORCE-to-terminate-autovacuum-p.patch application/octet-stream 4.1 KB
v4-0002-Add-test-for-DROP-DATABASE-FORCE-to-terminate-aut.patch application/octet-stream 3.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-10-15 02:16:08 Re: Fix numeric log() with an infinite value and 0<base<=1
Previous Message Haibo Yan 2026-10-15 02:01:43 Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan()