| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ivan babrou <ibobrik(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Millisecond-precision connect_timeout for libpq |
| Date: | 2013-07-05 20:09:49 |
| Message-ID: | 51D7280D.2050705@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/5/2013 1:01 PM, Josh Berkus wrote:
> If you are issuing a fresh connection for each sub-100ms query, you're
> doing it wrong anyway ...
> It's fairly common with certain kinds of apps, including Rails and PHP.
> This is one of the reasons why we've discussed having a kind of
> stripped-down version of pgbouncer built into Postgres as a connection
> manager. If it weren't valuable to be able to relocate pgbouncer to
> other hosts, I'd still say that was a good idea.
No kidding. I think a lot of -hackers forget that the web rules here and
the web is stateless, which means a huge performance loss for postgresql
unless we add yet another piece of software. Pre-forking here would
really help us.
JD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2013-07-05 20:18:32 | Re: Eliminating PD_ALL_VISIBLE, take 2 |
| Previous Message | Noah Misch | 2013-07-05 20:06:11 | Re: sepgsql and materialized views |