X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3AF2253589 for ; Wed, 13 Apr 2005 22:11:59 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 44378-06 for ; Thu, 14 Apr 2005 01:11:49 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by svr1.postgresql.org (Postfix) with ESMTP id 5F7925340D for ; Wed, 13 Apr 2005 22:11:48 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id 40so1782685nzk for ; Wed, 13 Apr 2005 18:11:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gRa2wptz/An6pxVw4zP/1+S4TpoDoyQtVIY7FgMNGEfgax2Pb9jXk3K2JJ6hw7TXbds0buKbulLRT4aGEyGx+pn7AehDyoAgz/o9bObIdyOa5arSNWv/36OQjVmBRh1VJR1risYxfApdW2kGs2WdTHXASyeYl7OYrPDJcQDNybI= Received: by 10.36.101.17 with SMTP id y17mr79387nzb; Wed, 13 Apr 2005 18:11:51 -0700 (PDT) Received: by 10.36.96.6 with HTTP; Wed, 13 Apr 2005 18:11:51 -0700 (PDT) Message-ID: Date: Thu, 14 Apr 2005 11:11:51 +1000 From: Slavisa Garic Reply-To: Slavisa Garic To: Richard Huxton Subject: Re: [NOVICE] Many connections lingering Cc: pgsql-performance@postgresql.org In-Reply-To: <425D58B7.5030909@archonet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2314.1113360715@sss.pgh.pa.us> <87u0mbjr02.fsf@stark.xeocode.com> <425D58B7.5030909@archonet.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.304 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/265 X-Sequence-Number: 11662 Hi, This looks very interesting. I'll give it a better look and see if the performance penalties pgpool brings are not substantial in which case this program could be very helpful, Thanks for the hint, Slavisa On 4/14/05, Richard Huxton wrote: > Slavisa Garic wrote: > > This is a serious problem for me as there are multiple users using our > > software on our server and I would want to avoid having connections > > open for a long time. In the scenario mentioned below I haven't > > explained the magnitute of the communications happening between Agents > > and DBServer. There could possibly be 100 or more Agents per > > experiment, per user running on remote machines at the same time, > > hence we need short transactions/pgsql connections. Agents need a > > reliable connection because failure to connect could mean a loss of > > computation results that were gathered over long periods of time. >=20 > Plenty of others have discussed the technical reasons why you are seeing > these connection issues. If you find it difficult to change your way of > working, you might find the pgpool connection-pooling project useful: > http://pgpool.projects.postgresql.org/ >=20 > HTH > -- > Richard Huxton > Archonet Ltd >