Re: EXPLAIN progress info

Gregory Stark <stark@enterprisedb.com> writes:
> I know I should still be looking at code from the March Commitfest but I was
> annoyed by this *very* FAQ:

>  http://archives.postgresql.org/pgsql-general/2008-04/msg00402.php

Seems like pg_relation_size and/or pgstattuple would solve his problem
better, especially since he'd not have to abort and restart the long
query to find out if it's making progress.  It'd help if pgstattuple
were smarter about "dead" vs uncommitted tuples, though.

            regards, tom lane