pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joseph Shraibman <jks@selectacast.net>
To: Clark, Joel <jclark@lendingtree.com>
Cc: 'sk@pobox.com' <sk@pobox.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Connection Pooling...(Repost)...please do help..
Date: Mon, 18 Dec 2000 20:18:57 -0500
Message-ID: <3A3EB781.80186971@selectacast.net> (raw)
References: <69F195289743D411B428009027E293C40267104F@CLTEXCH1>

"Clark, Joel" wrote:
> 
> I haven't found PG to have much connection overhead, why would open/closing
> a connection-per-query require server side connection pooling? 

Each connection causes the backend to fork.  With a heavy load you'll
feel the overhead of creating and closing so many connections.


-- 
Joseph Shraibman
jks@selectacast.net
Increase signal to noise ratio.  http://www.targabot.com



view thread (8+ messages)  latest in thread

Message-ID: <3A3EB781.80186971@selectacast.net>
Permalink:  ../3A3EB781.80186971@selectacast.net/
Also on:    postgresql.org/message-id/3A3EB781.80186971@selectacast.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: jks@selectacast.net, jclark@lendingtree.com, sk@pobox.com
  Subject: Re: Connection Pooling...(Repost)...please do help..
  In-Reply-To: <3A3EB781.80186971@selectacast.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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