Re: Millisecond-precision connect_timeout for libpq

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: ivan babrou <ibobrik(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Millisecond-precision connect_timeout for libpq
Date: 2013-07-08 16:40:29
Message-ID: 0D6497CD-0E5B-4C96-8D77-2DE623E40941@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 8, 2013, at 7:44 AM, ivan babrou <ibobrik(at)gmail(dot)com> wrote:

>> Can you tell me why having ability to specify more accurate connect
>> timeout is a bad idea?
>
> Nobody answered my question yet.

From an earlier post by Tom:

> What exactly is the use case for that? It seems like extra complication
> for something with little if any real-world usefulness.

So the answer is: extra complication.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-07-08 17:10:32 [9.4 CF 1] Week 3 report
Previous Message Dean Rasheed 2013-07-08 16:04:31 Re: psql tab completion for updatable foreign tables