From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Steve Atkins <steve(at)blighty(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL pre-fork speedup |
Date: | 2004-05-05 23:47:54 |
Message-ID: | 1083800873.88088.15.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I cannot tell if mod_pg_pool works across Apache forked backends or is
> > still bound to a single process. They state it is intended for sharing
> > connections across modules, so it is probably still backend specific.
>
> Have you looked at sqlrealy.sourceforge.net? IT looks like it might do
> what you need.
SQL Relay (and friends) do what I'm looking for in a round about way.
If you put it onto the webservers it would help -- but it would require
deployment of additional webservers to accommodate the increased load.
That can be accomplished if it helps drop the load on the DB machine.
But still uses resources unnecessarily.
I've not looked at sqlrelay but most of these things use a different
interface. That would work with the inhouse code but puts a damper on
the commercial software.
As a temporary step these types of things help. But it's still doesn't
really fix the problem of Apache not using real connection pooling.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-05-06 00:20:11 | Re: PostgreSQL pre-fork speedup |
Previous Message | Joe Conway | 2004-05-05 23:42:53 | Re: Multiple "selects" returned from a single stored procedure |