Re: [PATCHES] [pgsql-hackers-win32] explain analyze timings

2005-03-20 Thread Magnus Hagander
There is. I beleive QueryPerformanceCounter has sub-mirosecond resolution. Can we just replace gettimeofday() with a version that's basically: No, because it's also used for actual time-of-day calls. It'd be necessary to hack executor/instrument.c in particular. Here's a patch that does

Re: [PATCHES] [pgsql-hackers-win32] explain analyze timings

2005-03-20 Thread Simon Riggs
On Sun, 2005-03-20 at 14:42 +0100, Magnus Hagander wrote: There is. I beleive QueryPerformanceCounter has sub-mirosecond resolution. Can we just replace gettimeofday() with a version that's basically: No, because it's also used for actual time-of-day calls. It'd be necessary to hack

Re: [PATCHES] [pgsql-hackers-win32] explain analyze timings

2005-03-20 Thread Tom Lane
Magnus Hagander [EMAIL PROTECTED] writes: Here's a patch that does just this. This seems about the ugliest and most intrusive way you could have done it :-(. A judicious typedef and macro or two could eliminate most of the #ifdefs and code duplication, thereby preserving readability...

Re: [PATCHES] [pgsql-hackers-win32] explain analyze timings

2005-03-20 Thread Magnus Hagander
Here's a patch that does just this. This seems about the ugliest and most intrusive way you could have done it :-(. A judicious typedef and macro or two could eliminate most of the #ifdefs and code duplication, thereby preserving readability... Well, I certainly can't argue with that, now that

Re: [PATCHES] [pgsql-hackers-win32] explain analyze timings

2005-03-20 Thread Tom Lane
Magnus Hagander [EMAIL PROTECTED] writes: Here is a second attempt, hope it's closer to what you expected. Better --- patch applied with some minor editorialization. I still left two #ifdefs in there, for the addition and subtraction of timeval:s specifically. They could be made