X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 63DAC11F629D for ; Wed, 29 Mar 2006 23:59:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88382-08 for ; Wed, 29 Mar 2006 23:59:37 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.190]) by postgresql.org (Postfix) with ESMTP id 8FAF611F6299 for ; Wed, 29 Mar 2006 23:59:36 -0400 (AST) Received: by nproxy.gmail.com with SMTP id l24so240161nfc for ; Wed, 29 Mar 2006 19:59:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JXVJ2gfTl0Oo39RCZrCOmEgB2o2iFvIZniEaaa9O6ddM1v8LtLD766pt/Rbxecx/a3I8jT7JEfZUm57vNOdLN1HIeM4qMzTvd2MexZ6L2Sty2QwMbSb3f/htd+uMa8ynq2fKuGO5Gwoxgf6vnTYdGqNl3Bb7+v+b5u9P8NXclvE= Received: by 10.48.212.5 with SMTP id k5mr740859nfg; Wed, 29 Mar 2006 19:59:35 -0800 (PST) Received: by 10.49.26.20 with HTTP; Wed, 29 Mar 2006 19:59:35 -0800 (PST) Message-ID: Date: Thu, 30 Mar 2006 09:29:35 +0530 From: "Rajesh Kumar Mallah" To: "Salem Berhanu" Subject: Re: postgres and persistant connections (using Apache::DBI) Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.678 required=5 tests=[AWL=0.678] X-Spam-Score: 0.678 X-Spam-Level: X-Archive-Number: 200603/358 X-Sequence-Number: 21115 since it is not a postgresql issue i think we should not discuss it over here. i may persue it on pvt emails. regds mallah. On 3/30/06, Salem Berhanu wrote: > Rajesh, > Thanks for the suggestion. I tried what you told me. In my startup script= I > did > use Apache2::Status; > use Apache::DBI; > before any modules that use DB connect were loaded. > I also included the handler for perl-status in the conf file as you > mentioned. > However as I access different pages the database connection doesn't persi= st. > I check netstat on the db server and I see connections from the web serve= r > that appear and disappear. > I checked http://my_mod_perl_server/perl-status and it has a link that sa= ys > DBI connections but with no data in it. > Also I wasn't clear on why you are not using connect_on_init. > Thanks > Salem > > > >From: "Rajesh Kumar Mallah" > >To: "Salem Berhanu" > >CC: pgsql-admin@postgresql.org > >Subject: Re: [ADMIN] postgres and persistant connections (using > >Apache::DBI) > >Date: Wed, 29 Mar 2006 21:32:47 +0530 > > > >On 3/29/06, Salem Berhanu wrote: > > > I am trying to set up a persistent connection to a handful of postgre= s > >dbs > > > at startup using Apache::DBI (also using mod_perl) > > > Here is what I am doing but I am not sure how to check if it's workin= g > > > right. > > > > > > in httpd.conf I have > > > PerlRequire startup.pl > > > > > > in startup.pl I load all the necessary perl modules and also include = the > > > lines > > > > > > use Apache::DBI; > > > Apache::DBI->connect_on_init( host, login, password); > > > > > > This doesn't seem to make any difference. I was expecting to see > >database > > > connections when I restarted apache and that all queries would get > >handled > > > by these connections. Is this a wrong assumption? What is the > >expectation > > > and what would be a good test when setting up persistent connections = to > >a > > > postgres db? > > > >We use DBI connection pooling with postgres in mod_perl environment > >and it works fine. We however do not use connect_on_init as Apache::DBI > >docs say that all DBI->connect() anyway gets intercepted transparently. > > > >please take care that > > > >1. Make sure Apache::DBI is loaded before any module that issues a DB > >connect. > >you can even load Apache::DBI from httpd.conf by > >PerlRequire Apache::DBI > > > >2. You can know if Apache::DBI is effective or not by installing > >Apache::Status > >,load Apache::Status before Apache::DBI in that case and add a Location > >section in the httpd.conf like: > > > > > >--------------- httpd.conf--------------------- > >PerlModule Apache::Status > >PerlModule Apache::DBI > > > > > > SetHandler perl-script > > PerlHandler Apache::Status > > > >------------------------------------------------------ > >point your browser to http://your_mod_perl_server/perl-status > >and check the section about database conenctions. > > > >i am not sure if this info answers your question but > >i am describing something that works for me. > > > >regds > >Rajesh Kumar Mallah. > > > > > > > > > > > > > > > > > > > > > > > Thanks much > > > Salem > > > > > > > > > > > > ---------------------------(end of broadcast)------------------------= --- > > > TIP 2: Don't 'kill -9' the postmaster > > > > > >