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 97161563C9 for ; Fri, 25 Feb 2005 13:47:03 +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 56480-09 for ; Fri, 25 Feb 2005 13:46:57 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by svr1.postgresql.org (Postfix) with ESMTP id 4A16E55D73 for ; Fri, 25 Feb 2005 13:46:56 +0000 (GMT) Received: from jefftrout.com ([24.128.242.167]) by comcast.net (rwcrmhc13) with SMTP id <2005022513471501500l1rcme>; Fri, 25 Feb 2005 13:47:16 +0000 Received: (qmail 32528 invoked from network); 25 Feb 2005 13:47:15 -0000 Received: from waltham-nat.ma.lycos.com (HELO ?10.124.7.194?) (209.202.205.1) by 192.168.0.105 with SMTP; 25 Feb 2005 13:47:15 -0000 Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: performance pgsql From: Jeff Subject: Possible interesting extra information for explain analyze? Date: Fri, 25 Feb 2005 08:49:23 -0500 X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.93 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: X-Archive-Number: 200502/360 X-Sequence-Number: 10689 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). Some thing like: Seq Scan on boards (cost=0.00..686.30 rows=25430 width=0) (actual time=8.866..5407.693 rows=18636 loops=1 invisiblerows=8934983098294) This may help us to point out tuple bloat issues quicker... or it may give the developer enough of a clue to search around and find out he needs to vacuum... hmm.. but once we have an integrated autovacuum it will be a moot point..... Also another thing I started working on back in the day and hope to finish when I get time (that is a funny idea) is having explain analyze report when a step required the use of temp files. -- Jeff Trout http://www.jefftrout.com/ http://www.stuarthamm.net/