Re: Possible interesting extra information for explain analyze?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff <threshar(at)torgo(dot)978(dot)org>
Cc: performance pgsql <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Possible interesting extra information for explain analyze?
Date: 2005-02-25 16:05:10
Message-ID: 5599.1109347510@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jeff <threshar(at)torgo(dot)978(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2005-02-25 16:20:05 Re: Peformance Tuning Opterons/ Hard Disk Layout
Previous Message Stephan Szabo 2005-02-25 14:56:10 Re: IS NULL vs IS NOT NULL