From: | Gilles DAROLD <gilles(at)darold(dot)net> |
---|---|
To: | |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connection pooling |
Date: | 2001-01-26 11:39:19 |
Message-ID: | 3A7161E7.46CDF35B@darold.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Just to repeat that we have this stuff enabled using perl and mod_perl for a
very
long time. Just try to declare all your vars as global (without my or local)
and
see what's append between apache child process :-)
But as I know Apache::DBI doesn't do db connexion pooling, this is a
mistake.
It just allows you to create persitante connexion. But you can declare
multiple
persistante connection and do a random access to each one if your really
need
to play with that. Personnaly I never had to use that, but I think that with
a site
with a large amout of simoultaneous user it can be usefull.
Regards
Alex Pilosov wrote:
> On Thu, 25 Jan 2001, Frank Joerdens wrote:
>
> > How's that supposed to work? Apache is a multi-process web server.
> > Connection pooling over all Apache children that are currently alive on
> > a web server would require some kind of inter-process communication,
> > which I don't think Apache supports (am I mistaken?).
>
> That's what Apache 2.0 is about. It will be able to run in a multi-thread
> mode, or in multi-process mode with some data shared via shared memory.
>
> -alex
From | Date | Subject | |
---|---|---|---|
Next Message | James Thompson | 2001-01-26 14:49:56 | GNUe Forms 0.0.5 Released |
Previous Message | Pete Forman | 2001-01-26 11:12:32 | Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ] |