Re: generic options for explain

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generic options for explain
Date: 2009-05-24 12:44:58
Message-ID: 937d27e10905240544u736fff16j26b4af0e5100a984@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 24, 2009 at 12:31 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hello
>
> why we develop a new syntax?
>
> we should have a secondary function explain_query(query_string,
> option) that returns setof some. Next function should be
> explain_query_xml. I thing so for typical use EXPLAIN statement is
> enough. And for machine procession some new function should be
> perfect.

I agree. We shouldn't be overloading EXPLAIN with a new option every
time someone thinks of something new they'd like to see. XML EXPLAIN
output would obviously be extensible and machine readable. We could
easily produce a library of XSLT stylesheets to format the output in
different ways without cluttering the server with extra code. The
benefits to applications that want to read the output are also pretty
obvious.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-05-24 13:39:59 Re: generic options for explain
Previous Message Andres Freund 2009-05-24 11:43:51 Re: generic options for explain