X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C37D6538F0 for ; Thu, 31 Mar 2005 16:22:02 +0100 (BST) 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 64925-06 for ; Thu, 31 Mar 2005 15:21:57 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id D1A3D53747 for ; Thu, 31 Mar 2005 16:21:55 +0100 (BST) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 31 Mar 2005 09:21:55 -0600 Subject: Re: Many persistant client connections From: Scott Marlowe To: lst_hoe01@kwsoft.de Cc: pgsql-admin@postgresql.org In-Reply-To: <1112259136.424bba40cf286@webmail.kwsoft.de> References: <20050330090533.0dp4fmto0ckoossk@webtest.kwsoft.de> <60oed1rvr2.fsf@dba2.int.libertyrms.com> <1112259136.424bba40cf286@webmail.kwsoft.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1112282515.31277.69.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 31 Mar 2005 09:21:55 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/506 X-Sequence-Number: 17004 On Thu, 2005-03-31 at 02:52, lst_hoe01@kwsoft.de wrote: > Zitat von Chris Browne : > > > lst_hoe01@kwsoft.de writes: > > > i would like to know if there is something like the Oracle "shared > > > server" possible with PostgreSQL. I have searched the archives but > > > have not found any real discussion regarding this. > > > > > > We have two CTI applications opening 2-3 persistant connections to > > > the address server (PostgreSQL). With 100 clients we get around 400 > > > persistant connections eating up the server memory and have nothing > > > to work most of the time. > > > > Sounds like a case for looking into pgpool... > > > > > > > > pgpool is a connection pool system implemented in C that can allow > > sharing of connections for many cases like the one you describe. > > Thanks for the info. Is this the recommended way to handle many persistant > client connections or are there other opinions/possibilities? pgpool is one of several standard ways. It's a solid bit of software. It's also very useful in conjunction with Slony. jdbc connection pooling works well too. There are a few others I've seen but can't remember right off the top of my head.