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-02 15:08:06 |
Message-ID: | 46B1F356.6010207@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane wrote:
> 1Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>
>> Peter Koczan wrote:
>>
>>> There is a problem where connections listening for asynchronous notifies
>>> occasionally block for writing on ther server side and never finish,
>>>
>
>
>> Does the client read the async notifies? The write in the server will
>> block if the client doesn't keep up with reading the data.
>>
>
> Loss of network connectivity to the client (eg, timeout of a NAT
> mapping) seems like another plausible explanation.
>
> regards, tom lane
>
>
It's plausible, but unlikely for our network setup. We rarely use NAT
and if the client lost its network, this particular application (it's
Perl with GTK and DBD::Pg, by the way) tends to hang since it doesn't
try to re-establish a connection to the DB short of killing and
restarting it.
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-02 16:14:55 | Re: BUG #3504: Some listening sessions never return from writing, problems ensue |
Previous Message | Peter Koczan | 2007-08-02 15:04:11 | Re: BUG #3504: Some listening sessions never return from writing, problems ensue |