Re: PostgreSQL pre-fork speedup

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Steve Atkins <steve(at)blighty(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL pre-fork speedup
Date: 2004-05-05 20:36:13
Message-ID: 20040505203613.GE11196@ns.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Steve Atkins (steve(at)blighty(dot)com) wrote:
> On Wed, May 05, 2004 at 02:12:58PM -0400, Rod Taylor wrote:
> >
> > Most of it has been. It's the duty cycle. As stated in another email,
> > only about 20% of the work a script does is database related -- which
> > occurs all at one time. Even when all Apache backends are active, a
> > large number of connections will be idle but were used or will be used
> > at some point during the generation of that page.
> >
> > It really is an Apache fault -- but I don't think it can be fixed within Apache itself.
>
> http://apache.webthing.com/
>
> mod_pg_pool or mod_valet_sql - Apache modules to handle postgresql
> connection pools

Looks like what we need are functions in PHP or something which use the
functions provided by these apache modules, if they don't exist already
(as far as I know they don't?). Or whatever language it is that he's
using.

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-05-05 21:20:16 Re: initdb failure in CVS
Previous Message scott.marlowe 2004-05-05 20:14:39 Re: PostgreSQL pre-fork speedup