mirror of
https://github.com/postgres/postgres.git
synced 2025-05-03 22:24:49 +03:00
Fix statement_timeout on Win32 so that it properly treats micro-seconds
as micro-seconds, rather than as 100 microseconds, as it does now. This actually fixes all setitimer calls on Win32, but statement_timeout is the most visible fix. Backpatch to 8.1.X. 8.0 works as documented.
This commit is contained in:
parent
f896b5e146
commit
8f73c88c7c
@ -11,7 +11,7 @@
|
||||
* Portions Copyright (c) 1996-2006, PostgreSQL Global Development Group
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/port/win32/timer.c,v 1.9 2006/08/09 17:33:52 momjian Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/port/win32/timer.c,v 1.10 2006/08/09 17:47:03 momjian Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -56,7 +56,8 @@ pg_timer_thread(LPVOID param)
|
||||
timerCommArea.value.it_value.tv_usec == 0)
|
||||
waittime = INFINITE; /* Cancel the interrupt */
|
||||
else
|
||||
waittime = timerCommArea.value.it_value.tv_usec / 10 + timerCommArea.value.it_value.tv_sec * 1000;
|
||||
/* WaitForSingleObjectEx() uses milliseconds */
|
||||
waittime = timerCommArea.value.it_value.tv_usec / 1000 + timerCommArea.value.it_value.tv_sec * 1000;
|
||||
ResetEvent(timerCommArea.event);
|
||||
LeaveCriticalSection(&timerCommArea.crit_sec);
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user