From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: That EXPLAIN ANALYZE patch still needs work |
Date: | 2006-06-07 21:05:23 |
Message-ID: | 17395.1149714323@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Wed, Jun 07, 2006 at 11:34:30AM -0400, Tom Lane wrote:
>> timer interrupt routine does this once every few milliseconds:
> One issue is that on very fast queries, you'd get absolutely no data
> this way.
Yeah. Of course, on "very fast" queries you don't get very good data
from the existing method either --- with a machine fast enough to have
sub-microsecond plan node execution times, the accuracy of gettimeofday
really isn't good enough.
The other thing that was bothering me was whether disk I/O might be
undercounted by an interrupt-driven method. I kinda doubt that any
kernel will save up N interrupts that occur while the process is blocked
on a slow read() ... you'll probably get only one. So the whole idea
may be unworkable.
At the moment I think we need to revert the recent patch and go back
to the drawing board. Improving on the original implementation of
EXPLAIN ANALYZE is clearly not as easy as it looks.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-06-07 21:07:28 | Re: That EXPLAIN ANALYZE patch still needs work |
Previous Message | Tom Lane | 2006-06-07 20:56:27 | Re: That EXPLAIN ANALYZE patch still needs work |