From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff <threshar@torgo.978.org>
Cc: performance pgsql <pgsql-performance@postgresql.org>
Subject: Re: Possible interesting extra information for explain analyze?
Date: Fri, 25 Feb 2005 11:05:10 -0500
Message-ID: <5599.1109347510@sss.pgh.pa.us> (raw)
In-Reply-To: <ed07e0b06fee34124da83f065e19e486@torgo.978.org>
References: <ed07e0b06fee34124da83f065e19e486@torgo.978.org>
Jeff <threshar@torgo.978.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, threshar@torgo.978.org
Subject: Re: Possible interesting extra information for explain analyze?
In-Reply-To: <5599.1109347510@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox