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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
