Denis Perchine <[EMAIL PROTECTED]> writes:
> Looks like it tries to read on socket which is already closed from other
> side. And it seems like recv did not return in this case. Is this OK, or
> kernel bug?
Sounds like a kernel bug --- recv() should *always* return immediately
if the socket is
Hello,
I have quite strange problem. It's lsof -i -n -P
postmaste 20018 postgres6u IPv4 12241380 TCP
127.0.0.1:5432->127.0.0.1:6651 (CLOSE)
And there is no pair for it.
Backtrace of the backend shows:
(gdb) bt
#0 0x40198ba2 in recv () from /lib/libc.so.6
#1 0x80ab2c5 in pq_re
