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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Koczan" <pjkoczan(at)gmail(dot)com>
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-06 22:36:16
Message-ID: 3733.1186439776@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Peter Koczan" <pjkoczan(at)gmail(dot)com> writes:
> So, it looks like the app polls for async notifies every second. Hopefully
> you can glean some insight from that.

My guess is that some condition causes that to stop happening.

One way to monitor this from outside is to use strace to watch the app.
According to the above you should see a recv() attempt on the libpq
socket every second. I suspect that you won't see any more once the app
gets into the state where the recv-q is backing up. Looking at what
happens around the time of the last recv() might give some clues.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Koczan 2007-08-07 01:05:37 Re: BUG #3504: Some listening sessions never return from writing, problems ensue
Previous Message Heikki Linnakangas 2007-08-06 20:57:56 Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues