From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Peter Koczan <pjkoczan(at)gmail(dot)com> |
Cc: | tomas(at)tuxteam(dot)de, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3504: Some listening sessions never return from writing, problems ensue |
Date: | 2007-08-17 17:17:45 |
Message-ID: | 46C5D839.3080302@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Koczan wrote:
>> Hm. To me it looks like the first psql session isn't prepared to gather
>> async notifies (checking...) indeed, psql only checks for async notifies when
>> issuing commands (you don't have to issue a NOTIFY in "Connection 1" to
>> receive the pending notifies -- *any* request directed to the server would do).
>>
>> If you see the queue building up as above, the problem lies almost
>> certainly on the client not gathering the notifies. The backend is
>> obviously willing to talk to you :-)
>>
>> I'd look for the problem in the client library (It's DBD::Pg in your
>> "real" case, isn't it?)
>
> *Light bulb lights up* Ah....I see what's going on now.
>
> I think I have enough information to test and fix the problem on our
> end. Thank you all for your help and patience. This can be considered
> resolved.
Please share the ending with us, I'm really curious after following this
thread :).
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2007-08-17 19:03:22 | Re: BUG #3544: SQLException from JDBC driver |
Previous Message | Tom Lane | 2007-08-17 16:29:53 | Re: BUG #3548: When quickly switching between databases the server lags behind |