Re: Many persistant client connections
От | Scott Marlowe |
---|---|
Тема | Re: Many persistant client connections |
Дата | |
Msg-id | 1112282515.31277.69.camel@state.g2switchworks.com обсуждение исходный текст |
Ответ на | Re: Many persistant client connections (lst_hoe01@kwsoft.de) |
Список | 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 по дате отправления: