Horton

Re: EXPLAIN BUFFERS

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Euler Taveira de Oliveira <euler@timbira.com>, Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>, Greg Smith <greg@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2009-12-10T15:50:43Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Dec 10, 2009 at 9:03 AM, Euler Taveira de Oliveira
> <euler@timbira.com> wrote:
>> Why? If you want this information for all of your queries, you can always set
>> auto_explain.log_min_duration to 0. But if you're suggesting that we should
>> maintain log_statement_stats (that was not I understand from Tom's email [1]),
>> it's not that difficult to a change ShowBufferUsage().

> Mmm, OK, if Tom thinks we should rip it out, I'm not going to second-guess him.

Feel free to question that.  But it's ancient code and I'm not convinced
it still has a reason to live.  If you want to investigate the I/O
behavior of a particular query, you'll use EXPLAIN.  If you want to get
an idea of the system-wide behavior, you'll use the stats collector.
What use case is left for the backend-local counters?

			regards, tom lane