Re: Bad behavior of recv on already closed sockets.

Hello! > > It would be better to understand the issue f.e. trying to restore > > the history of this descriptor. > > How to do this? I mean what should I do to provide you with more information? I do not know exactly. It depends on curcumstances, frequency of the stalls and... your luck. 8) U

Re: Bad behavior of recv on already closed sockets.

Hi, > > 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? > > This smells like an unknown bug in kernel. > > It is unknown, hence there is no workaround (but upgrading to 2.4). > >

Re: Bad behavior of recv on already closed sockets.

Hello! > 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? This smells like an unknown bug in kernel. It is unknown, hence there is no workaround (but upgrading to 2.4). It would be

Bad behavior of recv on already closed sockets.

Hello, there was a small thread in PostgreSQL list about behavior of recv syscall on Linux 2.2.16. Does anyone have similar expirience? Why such things can happend? And how to workaround/fix this? -- Forwarded Message -- Subject: [HACKERS] Strange behavior of PostgreSQL on Li