| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Measure WaitLatch's timeout parameter in milliseconds, not micro |
| Date: | 2011-08-09 22:52:57 |
| Message-ID: | E1QqvAP-00072T-UJ@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/74d099494c5853a44188316ba117a8909b299d40
Modified Files
--------------
src/backend/access/transam/xlog.c | 2 +-
src/backend/port/unix_latch.c | 6 +++---
src/backend/port/win32_latch.c | 2 +-
src/backend/replication/syncrep.c | 2 +-
src/backend/replication/walsender.c | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-08-10 06:22:56 | pgsql: If backup-end record is not seen, and we reach end of recovery f |
| Previous Message | Tom Lane | 2011-08-09 19:31:07 | pgsql: Documentation improvement and minor code cleanups for the latch |