| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Greg Smith <greg(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: EXPLAIN BUFFERS |
| Date: | 2009-12-10 15:50:43 |
| Message-ID: | 14662.1260460243@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Dec 10, 2009 at 9:03 AM, Euler Taveira de Oliveira
> <euler(at)timbira(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-12-10 15:52:51 | Re: EXPLAIN BUFFERS |
| Previous Message | Zdenek Kotala | 2009-12-10 15:49:50 | Re: [patch] executor and slru dtrace probes |