Re: Connection pooling - Mailing list pgsql-general

From Valter Mazzola
Subject Re: Connection pooling
Date
Msg-id F25E2NSAW4eE2FGwQ2100000439@hotmail.com
Whole thread Raw
In response to Connection pooling  (Guillaume Lémery <glemery@comclick.com>)
Responses Re: Connection pooling  (Steve Leibel <stevel@bluetuna.com>)
List pgsql-general
Take a look to Apache::DBI

bye
valter


>From: Frank Joerdens <frank@joerdens.de>
>To: Gilles DAROLD <gilles@darold.net>
>CC: pgsql-general <pgsql-general@postgresql.org>
>Subject: Re: [GENERAL] Connection pooling
>Date: Thu, 25 Jan 2001 20:57:33 +0100
>
>On Thu, Jan 25, 2001 at 05:14:50PM +0100, Gilles DAROLD wrote:
> > Hi,
> >
> > With Apache/mod_perl it is very simple to enable DB connection
> > persistance.
> >
> > in your perl script :
> >
> > use vars qw($dbh);
> >
> > $dbh ||= DBI::connect($datasrc, $dbuser, $dbpwd);
> >
> > That create a persistance connection to your DB and you do not have to
> > care
> > about a pool of connection. Double pipe do all for you :-)
> >
> > But if you really want a pool just create an array of this kind of
>global
> > var at startup
> > and switch to any indices as you want.
>
>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?).
>
>Regards, Frank

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: timestamp calculations
Next
From: Karel Zak
Date:
Subject: Re: backend closing connections while executing...