From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
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 22:12:04 |
Message-ID: | 1083795123.60668.49.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Doug McNaught | 2004-05-05 22:18:25 | Re: Postgres Optimization: IO and Data Organization |
Previous Message | Alvaro Herrera | 2004-05-05 22:08:15 | Re: Multiple Xids in PGPROC? |