Re: EXPLAIN progress info - Mailing list pgsql-patches

From Tom Lane
Subject Re: EXPLAIN progress info
Date
Msg-id 8902.1207692153@sss.pgh.pa.us
Whole thread Raw
In response to EXPLAIN progress info  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: EXPLAIN progress info  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-patches
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

pgsql-patches by date:

Previous
From: David Fetter
Date:
Subject: Fix \dT enum in psql
Next
From: Gregory Stark
Date:
Subject: Re: EXPLAIN progress info