| 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-02 16:14:55 |
| Message-ID: | 12248.1186071295@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:
> Heikki Linnakangas wrote:
>> 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.
>>
> Well, the client updates it's GUI properly no matter whether the
> listening session is blocked or not (it's an ongoing tail of requests).
> Overtly from the client side, it's completely transparent. Is there any
> way I can tell definitively from the client side whether or not it's
> actually reading the async notifies?
netstat's Recv-Q column would probably reflect it if the client is
failing to consume messages. The send queue on the server side would be
worth checking too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Koczan | 2007-08-02 19:06:51 | Re: BUG #3504: Some listening sessions never return from writing, problems ensue |
| Previous Message | Peter Koczan | 2007-08-02 15:08:06 | Re: BUG #3504: Some listening sessions never return from writing, problems ensue |