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

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE
Date: 2026-11-09 03:37:22
Message-ID: CABPTF7W8TtM4b2YFrGJwmiCa6gSV4XuKHo5AAJUcA3OQOeofgw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> There may be something with threading here, actually, we've
> mentioned that as we could not rely on PIDs anymore, should the switch
> to threads happen, then a concept of session number would be required.
> If it is 8-byte wide, the PID rotation concern is moot.

I don't follow this well. Does this mean that this is not a problem
after threading?

--
Regards,
Xuneng Zhou
HighGo Software Co., Ltd.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-11-09 03:42:52 Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE
Previous Message Stef Van Vlierberghe 2026-11-09 03:28:45 Re: Proposal to allow setting cursor options on Portals