Re: Millisecond-precision connect_timeout for libpq - Mailing list pgsql-hackers

From ivan babrou
Subject Re: Millisecond-precision connect_timeout for libpq
Date
Msg-id CANWdNRAByb7Hvi_wCrdT4ny-5UQGh4r8JFXBm_ojOjSA72_QWg@mail.gmail.com
Whole thread Raw
In response to Re: Millisecond-precision connect_timeout for libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Millisecond-precision connect_timeout for libpq
List pgsql-hackers
If you can figure out that postgresql is overloaded then you may
decide what to do faster. In our app we have very strict limit for
connect time to mysql, redis and other services, but postgresql has
minimum of 2 seconds. When processing time for request is under 100ms
on average sub-second timeouts matter.

On 5 July 2013 22:20, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> ivan babrou <ibobrik@gmail.com> writes:
>> Hi, guys! I made a quick patch to support floating number in
>> connect_timeout param for libpq.
>
> What exactly is the use case for that?  It seems like extra complication
> for something with little if any real-world usefulness.
>
>                         regards, tom lane



-- 
Regards, Ian Babrou
http://bobrik.name http://twitter.com/ibobrik skype:i.babrou



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [9.4 CF 1] The Commitfest Slacker List
Next
From: Tom Lane
Date:
Subject: Re: Millisecond-precision connect_timeout for libpq