Re: contrib/pg_stat_statements 1202 - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: contrib/pg_stat_statements 1202
Date
Msg-id 1d709ecc0812091001jb9e362emd28b656bf6831f7e@mail.gmail.com
Whole thread Raw
In response to contrib/pg_stat_statements 1202  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses contrib/pg_stat_statements 1212
List pgsql-hackers


On Tue, Dec 9, 2008 at 8:53 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Tue, Dec 9, 2008 at 12:44 PM, Greg Stark <greg.stark@enterprisedb.com> wrote:
> Yes this is one reasonable option, as is the idea of using XML or a table
> and making it the client's problem. Neither are going to happen for this
> release I think.

Agreed.
I 100% agree with that point. Thus I suggest output additional information into "explain analyze" since:
 1) it will require minimal code change
 2) it will be consistent with previous behaviour
 3) looks like a natural EXPLAIN's feature improvement
 4) will be anyway changed when "table" for explain will come


> And in any case it will always be useful to have an option to print all the
> available information anyways so we make as well do that with "verbose".

Sounds very nice.
Can I ask my question once again? 
Why don't you want to make "print all the info" the default output format?
As long as it comes to "pgsql-performance", they used to recommend: "please, provide EXPLAIN ANALYZE, and not just EXPLAIN".
If the default output format is not changed in 8.4, this will transform into "please, provide EXPLAIN ANALYZE VERBOSE, not just EXPLAIN ANALYZE or EXPLAIN". Do you really want that?


Regards,
Vladimir Sitnikov

pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: parallel restore vs. windows
Next
From: Tom Lane
Date:
Subject: Re: cvs head initdb hangs on unixware