X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 60119D1B55D for ; Thu, 30 Oct 2003 17:29:21 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 97293-06 for ; Thu, 30 Oct 2003 13:28:49 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id D1D6DD1B57E for ; Thu, 30 Oct 2003 13:28:48 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9UHSlit001115; Thu, 30 Oct 2003 12:28:47 -0500 (EST) To: Rob Nagler Cc: pgsql-performance@postgresql.org Subject: Re: vacuum locking In-reply-to: <16289.14916.51000.772555@gargle.gargle.HOWL> References: <16272.318.870000.93584@gargle.gargle.HOWL> <87d6ciy3bf.fsf@stark.dyndns.tv> <16288.19970.172547.319577@jump.bivio.com> <200310291655.07363.josh@agliodbs.com> <16289.14916.51000.772555@gargle.gargle.HOWL> Comments: In-reply-to Rob Nagler message dated "Thu, 30 Oct 2003 09:20:20 -0700" Date: Thu, 30 Oct 2003 12:28:47 -0500 Message-ID: <1113.1067534927@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/765 X-Sequence-Number: 4513 Rob Nagler writes: > When vacuum is running, it's going through the entire > database, and that pretty much trashes all other queries, especially > DSS queries. As always it is just software, and there's got to be > 80/20 solution. One thing that's been discussed but not yet tried is putting a tunable delay into VACUUM's per-page loop (ie, sleep N milliseconds after each heap page is processed, and probably each index page too). This might be useless or it might be the 80/20 solution you want. Want to try it and report back? regards, tom lane