From: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
---|---|
To: | "tomas(at)tuxteam(dot)de" <tomas(at)tuxteam(dot)de> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-17 16:19:44 |
Message-ID: | 4544e0330708170919ie3ac511q485eba1e1df95869@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> 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.
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-17 16:29:53 | Re: BUG #3548: When quickly switching between databases the server lags behind |
Previous Message | Tom Lane | 2007-08-17 15:04:43 | Re: error while starting database |