2010/9/27 Guillaume Du Pasquier guillaume.dupasqu...@sensometrix.ch:
In both cases, the client socket (pgadmin or my program) remains in
TIME_WAIT state.
I have used wireshark to sniff the TCP protocol.
We have at the end of a connection:
Client Server
--- FIN,ACK
On Mon, Sep 27, 2010 at 12:22 PM, Nicolas Barbier
nicolas.barb...@gmail.com wrote:
According to the Two Generals' Problem [1], one of the sides
necessarily doesn't know whether the other side has received its last
packet. Therefore, TCP lets one of the sides sit in TIME_WAIT status
for as long
To: Guillaume Du Pasquier
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] client socket TIME_WAIT state after PQfinish
2010/9/27 Guillaume Du Pasquier guillaume.dupasqu...@sensometrix.ch:
In both cases, the client socket (pgadmin or my program) remains in
TIME_WAIT state.
I have used wireshark
On Mon, Sep 27, 2010 at 12:56 PM, Guillaume Du Pasquier
guillaume.dupasqu...@sensometrix.ch wrote:
Dear Nicolas, Dear Robert,
Thank you for your quick answers.
We do not have such behavior using SSL, how do you explain it ?
I suppose that openssl is using the setsockopt SO_LINGER that
2010/9/27 Robert Haas robertmh...@gmail.com:
On Mon, Sep 27, 2010 at 12:56 PM, Guillaume Du Pasquier
guillaume.dupasqu...@sensometrix.ch wrote:
Our client runs on the same machine as the postgresql server.
Would it be possible to use PF_UNIX sockets ?
Yeah, actually that's the default, if
