Re: Millisecond-precision connect_timeout for libpq

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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ivan babrou <ibobrik(at)gmail(dot)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