X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2E7909DC820 for ; Wed, 18 Jan 2006 19:36:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 66875-06 for ; Wed, 18 Jan 2006 19:36:07 -0400 (AST) X-Greylist: delayed 04:20:13.639376 by SQLgrey- Received: from www.conducivetech.com (conducivetech.com [64.65.134.45]) by postgresql.org (Postfix) with ESMTP id 279269DC80D for ; Wed, 18 Jan 2006 19:36:03 -0400 (AST) Received: from dentaku.sight-n-sound.com (dentaku.sight-n-sound.com [198.107.31.201]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by www.conducivetech.com (Postfix) with ESMTP id 7D3201838E for ; Wed, 18 Jan 2006 15:36:05 -0800 (PST) From: Michael Crozier To: pgsql-performance@postgresql.org Subject: Re: Autovacuum / full vacuum (off-topic?) Date: Wed, 18 Jan 2006 15:36:04 -0800 User-Agent: KMail/1.8.3 References: <200601181115.51850.crozierm@conducivetech.com> <20060118225257.GY17896@pervasive.com> In-Reply-To: <20060118225257.GY17896@pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601181536.04758.crozierm@conducivetech.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.144 required=5 tests=[AWL=0.144] X-Spam-Score: 0.144 X-Spam-Level: X-Archive-Number: 200601/320 X-Sequence-Number: 16798 On Wednesday 18 January 2006 14:52 pm, Jim C. Nasby wrote: > I think it's a good idea, but you should take a look at the recently > added functionality that allows you to investigate the contests of the > FSM via a user function (this is either in 8.1 or in HEAD; I can't > remember which). I will look at this when time allows. Perhaps there is a combination of triggers on stat tables and asynchronous notifications that would provide this functionality without getting too deep into the vacuum's transaction logic? Were it too integrated with the vacuum, it would likely be too much for contrib/, I assume. thanks, Michael