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 6E02156380 for ; Fri, 25 Feb 2005 16:04:53 +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 09812-06 for ; Fri, 25 Feb 2005 16:04:50 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E802C563B4 for ; Fri, 25 Feb 2005 16:04:49 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1PG5Bv6005600; Fri, 25 Feb 2005 11:05:11 -0500 (EST) To: Jeff Cc: performance pgsql Subject: Re: Possible interesting extra information for explain analyze? In-reply-to: References: Comments: In-reply-to Jeff message dated "Fri, 25 Feb 2005 08:49:23 -0500" Date: Fri, 25 Feb 2005 11:05:10 -0500 Message-ID: <5599.1109347510@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/362 X-Sequence-Number: 10691 Jeff writes: > Given some recent posts / irc issues with dead tuple bloat.. > And given that a lot of these people have at least been smart enough to > explain analyze would it be A. possible B. useful C. None of the above > to have various "scan" nodes of explain analyze also report how many > invisible / dead tuples they had to disqualify (Just to clarify, they > matched the search criteria, but were invisible due to MVCC rules). I think this would not help a whole lot because (particularly on indexscans) you won't get a very accurate picture of the true extent of bloat. The contrib/pgstattuple utility is more useful for measuring that sort of thing. regards, tom lane