Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: "Aya Iwata (Fujitsu)" <iwata(dot)aya(at)fujitsu(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE
Date: 2026-11-10 19:24:43
Message-ID: CAN4CZFPx-dOZCwEcOegD00Aj4Ww_7KW2LD05OrkOFBHT1pEhew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 10 Nov 2026, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> This last sentence should be gone. There is no point in sticking
> comments for things that are non-conditions to begin with. This was
> clearly AI-generated, as the kind of things that agents like adding
> for nothing based on solely the input provided..

Eh, sorry about that, looks like I managed to skim over this comment
without reading it properly. Removed.

On Tue, 10 Nov 2026, Iwata, Aya <iwata(dot)aya(at)jp(dot)fujitsu(dot)com> wrote:
> “A signal is sent directly to the worker so that it can be restarted according to the worker's bgw_restart_time setting.”

I also edited that part.

v5 is only these two comment changes compared to v3.

Attachment Content-Type Size
v5-0001-Fix-restart-of-interruptible-bgworkers-after-data.patch text/x-patch 8.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2026-11-10 19:27:02 Re: extension_control_path: ignore empty elements and deduplicate directories
Previous Message Greg Burd 2026-11-10 18:49:48 Re: ZSTD TOAST compression, and an extensible compression method encoding