Re: BUG #3504: Some listening sessions never return from writing, problems ensue

From: Peter Koczan <pjkoczan(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3504: Some listening sessions never return from writing, problems ensue
Date: 2007-08-03 21:40:07
Message-ID: 46B3A0B7.8020700@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I think the code is somehow interrupt based, but I don't know. I've
asked the primary maintainer of the program to look into this with me.
We should have more insight by early next week.

Peter

Tom Lane wrote:
> "Peter Koczan" <pjkoczan(at)gmail(dot)com> writes:
>
>> This app uses Perl/DBD::Pg, and the code is basically:
>>
>
>
>> while ($dbh->func('pg_notifies')) {
>> # do stuff
>> }
>>
>
> If I'm not mistaken, that loop would process all the currently available
> notify messages and then fall out. So the real question is what's
> around this --- what conditions will make the program come back to this
> loop periodically? Or not do so?
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Adam 2007-08-04 08:48:58 BUG #3511: timeofday()::timestamp failing on Saturday when using australian_timezones = on
Previous Message Vlad ROMASCANU 2007-08-03 16:02:34 Re: BUG #2393: update fails with unique constraint violation