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

On Mon, Nov 9, 2026 at 11:42 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Nov 09, 2026 at 11:37:22AM +0800, Xuneng Zhou wrote:
> >> 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?
>
> Under a threading infrastructure, PIDs have no meaning. So, assuming
> that a concept of session IDs is used to replace how we internally
> track each thread for the SQL interface, and assuming that this is 8
> byte wide, then the PID wraparound concerns would be entirely gone.
> This relies on three ifs.

Thanks. It's clear to me now.

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