Re: generic options for explain - Mailing list pgsql-hackers

From Tom Lane
Subject Re: generic options for explain
Date
Msg-id 3331.1243263773@sss.pgh.pa.us
Whole thread Raw
In response to Re: generic options for explain  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: generic options for explain  ("Massa, Harald Armin" <chef@ghum.de>)
Re: generic options for explain  (David Fetter <david@fetter.org>)
Re: generic options for explain  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> This is all much more complicated than what I proposed, and I fail to
> see what it buys us.  I'd say that you're just reinforcing the point I
> made upthread, which is that insisting that XML is the only way to get
> more detailed information will just create a cottage industry of
> beating that XML output format into submission.

The impression I have is that (to misquote Churchill) XML is the worst
option available, except for all the others.  We need something that can
represent a fairly complex data structure, easily supports addition or
removal of particular fields in the structure (including fields not
foreseen in the original design), is not hard for programs to parse,
and is widely supported --- ie, "not hard" includes "you don't have to
write your own parser, in most languages".  How many realistic
alternatives are there?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: No sanity checking performed on binary TIME parameters.
Next
From: Joshua Tolley
Date:
Subject: Re: generic options for explain