From: | Cédric Villemain <cedric(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, ivan babrou <ibobrik(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Millisecond-precision connect_timeout for libpq |
Date: | 2013-07-08 17:13:38 |
Message-ID: | 201307081913.39070.cedric@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Le lundi 8 juillet 2013 18:40:29, David E. Wheeler a écrit :
> 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.
for something that must go through a pooler anyway.
You can have a look at pgbouncer: query_wait_timeout parameter for example.
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-07-08 17:17:56 | Re: Improving avg performance for numeric |
Previous Message | Josh Berkus | 2013-07-08 17:11:36 | Re: [PERFORM] In progress INSERT wrecks plans on table |