Re: Adding qualification conditions to EXPLAIN output

From: Masaru Sugawara <rk73(at)sea(dot)plala(dot)or(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adding qualification conditions to EXPLAIN output
Date: 2002-03-10 05:43:14
Message-ID: 20020310144139.678F.RK73@sea.plala.or.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 09 Mar 2002 18:02:17 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I have been fooling around with adding decompiled display of plan
> qualification conditions to EXPLAIN output. With this, you can
> for example tell the difference between indexscanned and
> not-indexscanned clauses, without having to dig through EXPLAIN
> VERBOSE dumps. Here is an example motivated by Rob Hoopman's
> recent query on pgsql-general:
...
> Question for the group: does this seem valuable enough to put into the
> standard EXPLAIN output, or should it be a special option? I can
> imagine showing it only in EXPLAIN VERBOSE's summary display, or adding
> a GUC variable to enable it, or adding another option keyword to
> EXPLAIN, but I don't much want to do any of those things. On the other
> hand, maybe this stuff won't make any sense to non-experts anyway.
> Thoughts?

AFAIC, I'd think adding another keyword is better if the standard
EXPLAIN is extended.

e.g.
EXPLAIN keyword SELECT * FROM ...
EXPLAIN ANALYZE keyword SELECT * FROM ...

Regards,
Masaru Sugawara

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-03-10 06:01:37 Re: Index USING in pg_dump
Previous Message Lee Harr 2002-03-10 00:33:13 Re: bug in psql