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 Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/9f17ffd8660243382809b8023ff3d38fbfac4e8b Modified Files -------------- src/backend/access/transam/xlog.c | 4 +++- src/backend/port/unix_latch.c | 7 ++++--- src/backend/port/win32_latch.c | 10 +++------- src/backend/postmaster/pgarch.c | 5 +++-- src/backend/replication/syncrep.c | 2 +- src/backend/replication/walsender.c | 2 +- 6 files changed, 15 insertions(+), 15 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers