Re: Parsing output of EXPLAIN command in PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Αναστάσιος Αρβανίτης <tasosarvanitis(at)yahoo(dot)gr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing output of EXPLAIN command in PostgreSQL
Date: 2011-11-10 23:47:18
Message-ID: 19892.1320968838@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/10/2011 04:59 PM, Tom Lane wrote:
>> Nonetheless, it's solving the wrong problem. Any program that is being
>> written today to read EXPLAIN output should be written to read one of
>> the machine-readable formats.

> Umm, it *does* handle all the formats:

The point I'm trying to make is that translating the parts that handle
text into another language seems like wasted effort. depesz has a
specific problem to solve, namely wanting to accept emailed input from
users who are likely to send any format; and that requires him to expend
a lot of effort that is not likely to be necessary in any other setting.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2011-11-10 23:53:13 Re: psql expanded auto
Previous Message Josh Kupershmidt 2011-11-10 23:42:53 Re: proposal: psql concise mode