pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Many persistant client connections
4+ messages / 3 participants
[nested] [flat]

* Many persistant client connections
@ 2005-03-30 07:05  lst_hoe01@kwsoft.de
  0 siblings, 1 reply; 4+ messages in thread

From: lst_hoe01@kwsoft.de @ 2005-03-30 07:05 UTC (permalink / raw)
  To: pgsql-admin

Hello

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.

Thanxs for any help

Andreas




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Many persistant client connections
@ 2005-03-30 15:36  Chris Browne <cbbrowne@acm.org>
  parent: lst_hoe01@kwsoft.de
  0 siblings, 1 reply; 4+ messages in thread

From: Chris Browne @ 2005-03-30 15:36 UTC (permalink / raw)
  To: pgsql-admin

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.
-- 
(format nil "~S@~S" "cbbrowne" "cbbrowne.com")
http://www3.sympatico.ca/cbbrowne/postgresql.html
"The  present  need for  security  products far exceeds  the number of
individuals    capable of    designing  secure  systems. Consequently,
industry  has resorted to  employing folks  and purchasing "solutions"
from vendors that shouldn't be let near a project involving securing a
system."  -- Lucky Green



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Many persistant client connections
@ 2005-03-31 08:52  lst_hoe01@kwsoft.de
  parent: Chris Browne <cbbrowne@acm.org>
  0 siblings, 1 reply; 4+ messages in thread

From: lst_hoe01@kwsoft.de @ 2005-03-31 08:52 UTC (permalink / raw)
  To: pgsql-admin

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?

Regards

Andreas




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Many persistant client connections
@ 2005-03-31 15:21  Scott Marlowe <smarlowe@g2switchworks.com>
  parent: lst_hoe01@kwsoft.de
  0 siblings, 0 replies; 4+ messages in thread

From: Scott Marlowe @ 2005-03-31 15:21 UTC (permalink / raw)
  To: lst_hoe01@kwsoft.de; +Cc: 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.



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2005-03-31 15:21 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-03-30 07:05 Many persistant client connections lst_hoe01@kwsoft.de
2005-03-30 15:36 ` Chris Browne <cbbrowne@acm.org>
2005-03-31 08:52   ` lst_hoe01@kwsoft.de
2005-03-31 15:21     ` Scott Marlowe <smarlowe@g2switchworks.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox