X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5BFB03A4448 for ; Wed, 3 Nov 2004 14:17:51 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60503-02 for ; Wed, 3 Nov 2004 14:17:42 +0000 (GMT) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by svr1.postgresql.org (Postfix) with SMTP id AECCB3A4409 for ; Wed, 3 Nov 2004 14:17:44 +0000 (GMT) Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@65.49.125.184 with login) by smtp101.rog.mail.re2.yahoo.com with SMTP; 3 Nov 2004 14:17:44 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 4066A404B; Wed, 3 Nov 2004 09:17:43 -0500 (EST) Date: Wed, 3 Nov 2004 09:17:43 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: Restricting Postgres Message-ID: <20041103141743.GA15499@phlogiston.dyndns.org> Mail-Followup-To: pgsql-performance@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/15 X-Sequence-Number: 8969 On Tue, Nov 02, 2004 at 11:52:12PM +0000, Martin Foster wrote: > Is there a way to restrict how much load a PostgreSQL server can take > before dropping queries in order to safeguard the server? I was Well, you could limit the number of concurrent connections, and set the query timeout to a relatively low level. What that ought to mean is that, under heavy load, some queries will abort. A -- Andrew Sullivan | ajs@crankycanuck.ca When my information changes, I alter my conclusions. What do you do sir? --attr. John Maynard Keynes