From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Rationalizing EXPLAIN VERBOSE output |
Date: | 2002-03-11 04:26:59 |
Message-ID: | 9916.1015820819@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> The other possibility is to make EXPLAIN output look like a SELECT
>> result. Not sure how hard this would be to do, but in the long run
>> I suppose that would be the direction to move in.
> You could internally rewrite it to something like
> select explain('select * from pg_class;');
Having looked, I think it wouldn't be that bad to call the regular
printtup.c routines directly. Assuming that the output model we
want is "one text column, with one row per line", it'd only be
necessary to fake up a correct TupleDesc and then form a HeapTuple
from each line of output. Lots less work than trying to rewrite
the query, I think.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-11 04:36:05 | Re: Rationalizing EXPLAIN VERBOSE output |
Previous Message | Peter Eisentraut | 2002-03-11 04:25:40 | Re: Rationalizing EXPLAIN VERBOSE output |