From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Rod Taylor <pg(at)rbt(dot)ca> |
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:23:23 |
Message-ID: | Pine.LNX.4.33.0405051723050.3650-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 5 May 2004, Rod Taylor wrote:
> > And, of course, most development environments (perl, php, java etc)
> > have their own language specific connection pooling solutions.
>
> Yes, the one for php is what I was thinking of when I made my statement.
> They work on a per backend basis as Apache does not allow for the type
> of communication between processes that would otherwise be required. A
> connection created by Apache backend A cannot be used by Apache backend
> B.
>
> Java is an example where it is done well, but the language decision was
> made long before I joined the firm.
>
> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-05-05 23:42:53 | Re: Multiple "selects" returned from a single stored procedure |
Previous Message | terr | 2004-05-05 23:14:40 | database read/write from applications code Request for advice |