pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John A Meinel <john@johnmeinel.com>
To: Martin Foster <martin@ethereal-realms.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Wed, 03 Nov 2004 17:25:27 -0600
Message-ID: <418968E7.40700@johnmeinel.com> (raw)
In-Reply-To: <41894CD9.8090308@ethereal-realms.org>
References: <M4Vhd.85137$9b.34888@edtnps84>
	<1099509684.4320.2.camel@localhost.localdomain>
	<41894CD9.8090308@ethereal-realms.org>

Martin Foster wrote:
> Simon Riggs wrote:
> 
>> On Tue, 2004-11-02 at 23:52, Martin Foster wrote:
[...]

> I've seen this behavior before when restarting the web server during 
> heavy loads.    Apache goes from zero connections to a solid 120, 
> causing PostgreSQL to spawn that many children in a short order of time 
> just to keep up with the demand.
> 

But wouldn't limiting the number of concurrent connections do this at 
the source. If you tell it that "You can at most have 20 connections" 
you would never have postgres spawn 120 children.
I'm not sure what apache does if it can't get a DB connection, but it 
seems exactly like what you want.

Now, if you expected to have 50 clients that all like to just sit on 
open connections, you could leave the number of concurrent connections high.

But if your only connect is from the webserver, where all of them are 
designed to be short connections, then leave the max low.

The other possibility is having the webserver use connection pooling, so 
it uses a few long lived connections. But even then, you could limit it 
to something like 10-20, not 120.

John
=:->

Attachments:

  signature.asc (application/pgp-signature, 252B) download

view thread (34+ messages)  latest in thread

Message-ID: <418968E7.40700@johnmeinel.com>
Permalink:  ../418968E7.40700@johnmeinel.com/
Also on:    postgresql.org/message-id/418968E7.40700@johnmeinel.com

 · 

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-performance@postgresql.org
  Cc: john@johnmeinel.com, martin@ethereal-realms.org
  Subject: Re: Restricting Postgres
  In-Reply-To: <418968E7.40700@johnmeinel.com>

* 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