From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Where does the time go? |
Date: | 2006-03-25 10:52:10 |
Message-ID: | 1143283930.24487.972.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Wed, 2006-03-22 at 21:59 -0500, Tom Lane wrote:
> I'm betting that a
> big part of your issue is that the EXPLAIN ANALYZE instrumentation
> overhead is (1) significant
I would like to implement an additional mode for EXPLAIN ANALYZE that
does no timing instrumentation at all. Most of the time just looking for
differences between estimated and actual row counts is all you need.
For long queries, the additional time can make the execution infeasible,
yet frequently they are the ones you want to see the output for.
EXPLAIN ANALYZE NOTIMING sounds a little dry, any ideas?
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Dhanaraj M - Sun Microsystems | 2006-03-25 12:19:27 | How to create the patch? |
Previous Message | Joshua D. Drake | 2006-03-25 05:51:21 | Re: [SUGGESTION] CVSync |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-03-25 12:24:00 | Re: [PATCHES] Automatically setting work_mem |
Previous Message | Kris Jurka | 2006-03-24 18:09:26 | Re: [PERFORM] WAL logging of SELECT ... INTO command |