| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: EXPLAIN VERBOSE vs resjunk output columns |
| Date: | 2009-08-22 00:56:12 |
| Message-ID: | 407d949e0908211756h519345bv611614451cca6c38@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 22, 2009 at 1:37 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> You can see that from the fact that the estimated row width is
> 8 bytes (two integers) ... but tenthous is nowhere to be seen in the
> Output: line.
+1 for self-consistent output. If we're including their size in
"width" then they should be in the output list. If there was some way
to mark the junk columns so users could tell which columns are being
used higher up and which aren't -- which might be helpful if there are
ambiguous names -- then that might be good. Nothing comes to mind
offhand that wouldn't just be a lot of clutter though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-08-22 01:01:35 | Re: Feedback about Drupal SQL debugging |
| Previous Message | Stephen Frost | 2009-08-22 00:53:05 | Re: EXPLAIN VERBOSE vs resjunk output columns |