Re: BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return

Kiran Khatke <kirankhatke23may(at)gmail(dot)com> writes:
> One of the thread of DBMGR Daemon is waiting for the result of poll()
> function.
> poll() was called by pgSocketCheck(). So pqSocketCheck() didn't return,
> hung in poll().
> Below is the backtrace.

Well, it's waiting for the query to finish, or so it thinks. Did you
look at what the server thinks the session is doing?

Your reference to multiple threads is a red flag to me. Very often
we see people whose programs try to use the same PGconn object from
multiple threads. That doesn't work --- and libpq does not have any
internal mutexes that would prevent the object's state from getting
messed up by concurrent operations. So a plausible theory is that
this PGconn was used concurrently, and now this particular thread
is stuck because the object's state is corrupt (ie, it shows the
query as busy but the server doesn't think so).

It might be worth enabling log_statement = all on the server side
and then watching the server log to see what seems to be happening
from that end.

regards, tom lane