Re: PostgreSQL pre-fork speedup - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: PostgreSQL pre-fork speedup
Date
Msg-id Pine.LNX.4.33.0405051723050.3650-100000@css120.ihs.com
Whole thread Raw
In response to Re: PostgreSQL pre-fork speedup  (Rod Taylor <pg@rbt.ca>)
Responses Re: PostgreSQL pre-fork speedup  (Rod Taylor <pg@rbt.ca>)
List 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.



pgsql-hackers by date:

Previous
From: terr@terralogic.net
Date:
Subject: database read/write from applications code Request for advice
Next
From: Joe Conway
Date:
Subject: Re: Multiple "selects" returned from a single stored procedure