-
- Downloads
Measure WaitLatch's timeout parameter in milliseconds, not microseconds.
The original definition had the problem that timeouts exceeding about 2100 seconds couldn't be specified on 32-bit machines. Milliseconds seem like sufficient resolution, and finer grain than that would be fantasy anyway on many platforms. Back-patch to 9.1 so that this aspect of the latch API won't change between 9.1 and later releases. Peter Geoghegan
Showing
- src/backend/access/transam/xlog.c 3 additions, 1 deletionsrc/backend/access/transam/xlog.c
- src/backend/port/unix_latch.c 4 additions, 3 deletionssrc/backend/port/unix_latch.c
- src/backend/port/win32_latch.c 3 additions, 7 deletionssrc/backend/port/win32_latch.c
- src/backend/postmaster/pgarch.c 3 additions, 2 deletionssrc/backend/postmaster/pgarch.c
- src/backend/replication/syncrep.c 1 addition, 1 deletionsrc/backend/replication/syncrep.c
- src/backend/replication/walsender.c 1 addition, 1 deletionsrc/backend/replication/walsender.c
Loading
Please register or sign in to comment