Re: Many persistant client connections

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: lst_hoe01(at)kwsoft(dot)de
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Many persistant client connections
Date: 2005-03-31 15:21:55
Message-ID: 1112282515.31277.69.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, 2005-03-31 at 02:52, lst_hoe01(at)kwsoft(dot)de wrote:
> Zitat von Chris Browne <cbbrowne(at)acm(dot)org>:
>
> > lst_hoe01(at)kwsoft(dot)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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2005-03-31 15:29:44 Re: connectivity to database been an issue for me.
Previous Message Tsirkin Evgeny 2005-03-31 14:12:36 Re: locale and character set