Re: Rationalizing EXPLAIN VERBOSE output

From: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rationalizing EXPLAIN VERBOSE output
Date: 2002-03-11 05:55:45
Message-ID: Pine.LNX.4.21.0203111641100.28740-100000@linuxworld.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 11 Mar 2002, Bruce Momjian wrote:

> Gavin Sherry wrote:
> > On Mon, 11 Mar 2002, Bruce Momjian wrote:
> >
> > > > I agree. This is fine under Unix, but command arguments are not really a
> > > > grammar. Yacc doesn't enjoy terminal repetition and for good reason: it
> > > > usually suggests a clumsy grammar.
> > > >
> > > > Personally, I think that Tom's code should go into standard EXPLAIN.
> > >
> > > I am confused. Which grammar do you like?
> >
> > Neither =).
>
> OK, would you suggest one?

I don't think there needs to be a grammar change. I think that Tom's
qualification changes should go into non-verbose EXPLAIN and that pretty
vs. non-pretty debug just gets handled via debug_print_pretty.

The disadvantage of this is, of course, that users would want to be able
to change debug_print_pretty. I don't think that the solution to this is
another GUC variable though. I think it EXPLAIN output tables.

Yes, this results in a grammar change but IMHO users get a lot more out of
this modification than levels, since they can store/manipulate EXPLAIN
output if they choose. Naturally, there would be a psql \command tie in.

This is does some of what I want to get into a release some time in the
future: auditing. Perhaps storage of explain output would be more suited
to that. Just my 2 cents.

Gavin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-03-11 06:18:10 Re: Rationalizing EXPLAIN VERBOSE output
Previous Message Gavin Sherry 2002-03-11 05:36:36 Re: Rationalizing EXPLAIN VERBOSE output