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

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: postgres process got stuck in "notify interrupt waiting" status
Date: 2012-09-05 15:17:32
Message-ID: CA+jMWoePaBLqZcyNVCyFSs_rcAeH+AM7+hOog0_-UyQ4Wf9HKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Sep 5, 2012 at 7:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Having said that, a kill -9 on an individual backend (*not* the
> postmaster) should be safe enough, if you don't mind the fact that
> it'll kill all your other sessions too.
>

Got it, thanks.

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

Best,
-at

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2012-09-05 15:29:45 Re: postgres process got stuck in "notify interrupt waiting" status
Previous Message Johan Nel 2012-09-05 15:15:24 Re: alter view, add/drop column