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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Aleksey Tsalolikhin" <atsaloli(dot)tech(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "John R Pierce" <pierce(at)hogranch(dot)com>, <pgsql-general(at)postgresql(dot)org>,"Craig Ringer" <ringerc(at)ringerc(dot)id(dot)au>
Subject: Re: postgres process got stuck in "notify interrupt waiting" status
Date: 2012-09-05 15:29:45
Message-ID: 504729990200002500049EAA@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-09-05 15:33:45 Re: postgres process got stuck in "notify interrupt waiting" status
Previous Message Aleksey Tsalolikhin 2012-09-05 15:17:32 Re: postgres process got stuck in "notify interrupt waiting" status