Re: client socket TIME_WAIT state after PQfinish - Mailing list pgsql-hackers

From Robert Haas
Subject Re: client socket TIME_WAIT state after PQfinish
Date
Msg-id AANLkTik17K1vawqZeFB0E-chO4PrfQKYabqo0A053qDW@mail.gmail.com
Whole thread Raw
In response to Re: client socket TIME_WAIT state after PQfinish  (Nicolas Barbier <nicolas.barbier@gmail.com>)
List pgsql-hackers
On Mon, Sep 27, 2010 at 12:22 PM, Nicolas Barbier
<nicolas.barbier@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 as any packets could in principle survive on the network
> (typically defined as 2 minutes on IP networks IIRC), and potentially
> disturb a new connection between the same (dst IP, dst port, src IP,
> src port) combination.

In other words, this is the way TCP is designed to work, not something
specific to PostgreSQL.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: trailing whitespace in psql table output
Next
From: Robert Haas
Date:
Subject: Re: Improving prep_buildtree used in VPATH builds