Re: postgres process got stuck in "notify interrupt waiting" status

Aleksey Tsalolikhin <atsaloli.tech@gmail.com> wrote:

> Why will it kill all your other sessions too?  Isn't there a
> separate backend process for each session?

When stopped that abruptly, the process has no chance to clean up
its pending state in shared memory.  A fresh copy of shared memory
is needed, so it is necessary to effectively do an immediate restart
on the whole PostgreSQL instance.

-Kevin