Re: Many persistant client connections - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Many persistant client connections
Date
Msg-id 1112282515.31277.69.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: Many persistant client connections  (lst_hoe01@kwsoft.de)
List pgsql-admin
On Thu, 2005-03-31 at 02:52, lst_hoe01@kwsoft.de wrote:
> Zitat von Chris Browne <cbbrowne@acm.org>:
>
> > 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...
> >
> >   <http://pgfoundry.org/projects/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.

pgsql-admin by date:

Previous
From: Tsirkin Evgeny
Date:
Subject: Re: locale and character set
Next
From: Scott Marlowe
Date:
Subject: Re: connectivity to database been an issue for me.