Re: EXPLAIN progress info

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: EXPLAIN progress info
Date: 2008-04-08 22:02:33
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-patches

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


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

In response to


Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-08 22:07:56 Re: [PATCHES] libpq type system 0.9a
Previous Message Tom Lane 2008-04-08 21:56:18 Re: Concurrent psql API