X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 02784D1D524 for ; Fri, 21 Nov 2003 23:05:27 +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 05523-01 for ; Fri, 21 Nov 2003 19:04:58 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 68AF7D1B53A for ; Fri, 21 Nov 2003 19:04:55 -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 hALN4u19015609; Fri, 21 Nov 2003 18:04:57 -0500 (EST) To: josh@agliodbs.com Cc: "Matthew T. O'Connor" , Robert Treat , Shridhar Daithankar , pgsql-performance@postgresql.org, PostgreSQL-development Subject: Re: [HACKERS] More detail on settings for pgavd? In-reply-to: <200311211323.19003.josh@agliodbs.com> References: <200311181558.45847.josh@agliodbs.com> <200311210909.00978.josh@agliodbs.com> <3FBE8289.1040009@zeut.net> <200311211323.19003.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Fri, 21 Nov 2003 13:23:18 -0800" Date: Fri, 21 Nov 2003 18:04:56 -0500 Message-ID: <15608.1069455896@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/197 X-Sequence-Number: 4757 Josh Berkus writes: > BTW, do we have any provisions to avoid overlapping vacuums? That is, to > prevent a second vacuum on a table if an earlier one is still running? Yes, VACUUM takes a lock that prevents another VACUUM on the same table. regards, tom lane