Re: Millisecond-precision connect_timeout for libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ivan babrou <ibobrik(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Millisecond-precision connect_timeout for libpq
Date: 2013-07-05 19:26:30
Message-ID: 25212.1373052390@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ivan babrou <ibobrik(at)gmail(dot)com> writes:
> 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.

If you are issuing a fresh connection for each sub-100ms query, you're
doing it wrong anyway ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ivan babrou 2013-07-05 19:47:16 Re: Millisecond-precision connect_timeout for libpq
Previous Message Josh Berkus 2013-07-05 19:09:04 Re: [9.4 CF 1] The Commitfest Slacker List