Re: Connection pooling.

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jeffery Collins <collins(at)onyx-technologies(dot)com>, pgsql-hackers(at)hub(dot)org
Subject: Re: Connection pooling.
Date: 2000-07-12 05:35:00
Message-ID: 20000711223500.Z25571@fw.wintelcom.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [000711 21:31] wrote:
> > It seems like a first step would be to just have postmaster cache unused
> > connections. In other words if a client closes a connection, postmaster
> > keeps the connection and the child process around for the next connect
> > request. This has many of your advantages, but not all. However, it seems
> > like it would be simpler than attempting to multiplex a connection between
> > multiple clients.
> >
>
> This does seem like a good optimization.

I'm not sure if the postmaster is needed besideds just to fork/exec
the backend, if so then when a backend finishes it can just call
accept() on the listening socket inherited from the postmaster to
get the next incomming connection.

-Alfred

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-07-12 05:40:38 Re: Performance problem in aset.c
Previous Message Alfred Perlstein 2000-07-12 05:33:12 Re: Performance problem in aset.c