Re: pgbench duration option - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: pgbench duration option
Date
Msg-id 20080819110134.C6FD.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: pgbench duration option  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgbench duration option  (Alvaro Herrera <alvherre@commandprompt.com>)
[Review] pgbench duration option  ("Brendan Jurd" <direvus@gmail.com>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> My understanding is that it's basically "cheap PC hardware" (with clock
> interfaces based on old ISA bus specs) that has the issue in a
> significant way.  I wouldn't expect you to see it on a serious database
> server.  But lots of people still do development on cheap PC hardware,
> which is why I think this is worth worrying about.

Ok, I rewrote the patch to use SIGALRM instead of gettimeofday.

The only thing I worried about is portability issue. POSIX functions
like alarm() or setitimer() are not available at least on Windows.
I expect alarm() is available on all platforms except Win32 and
used CreateTimerQueue() instead on Win32 in the new patch.
(We have own implementation of setitimer() in the server core, but pgbench
 cannot use the function because it is a client application.)

Comments welcome and let me know if there are still some problems.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Improving non-joinable EXISTS subqueries
Next
From: Alvaro Herrera
Date:
Subject: Re: pgbench duration option