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, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE
Date: 2026-11-06 13:42:58
Message-ID: CAN4CZFNE_BOOGnbXyyPAyo0asRzJQLfkDg11ogjRX2CZd_7xYA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 06 Nov 2026, Iwata, Aya <iwata(dot)aya(at)jp(dot)fujitsu(dot)com> wrote:
> In that case, I believe this should be handled as a core
> feature rather than left to an extension.

Yes, I agree that this part is questionable, but to me this still
looks like the safest choice:

1. it can already be the case in other scenarios, so this is not
really new behavior
2. can the core for sure make the assumption that the bgworker will
want to reconnect to the same database again?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-11-06 13:50:19 Re: Require SSL connection to postgres for oauth
Previous Message Mario Karuza 2026-11-06 13:41:47 Re: Improve hash aggregate spilling by writing only the needed columns