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: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, 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 18:44:45
Message-ID: CA+jMWoe7rr86ZMHkZW3aie=Re8xmbpA-h=NFT+BiyFrAbhFUmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Sep 5, 2012 at 10:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> That sounded a bit fishy to me too. But unless you can reproduce it in
> something newer than 8.4.x, nobody's likely to take much of an interest.
> The LISTEN/NOTIFY infrastructure got completely rewritten in 9.0, so
> any bugs in the legacy version are probably just going to get benign
> neglect at this point ... especially if we don't know how to reproduce
> them.

Got it, thanks, Tom! Will urge our shop to upgrade to 9.1.

Best,
-at

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jam3 2012-09-05 18:49:49 Re: Where is the char and varchar length in pg_catalog for function input variables
Previous Message Edson Richter 2012-09-05 18:30:18 Moving several databases into one database with several schemas