pgsql: Widen the nLocks counts in local lock tables from int to int64.

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Widen the nLocks counts in local lock tables from int to int64.
Date: 2008-09-16 01:56:26
Message-ID: 20080916015626.B00A07545A4@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Widen the nLocks counts in local lock tables from int to int64. This
forestalls potential overflow when the same table (or other object, but
usually tables) is accessed by very many successive queries within a single
transaction. Per report from Michael Milligan.

Back-patch to 8.0, which is as far back as the patch conveniently applies.
There have been no reports of overflow in pre-8.3 releases, but clearly the
risk existed all along. (Michael's report suggests that 8.3 may consume lock
counts faster than prior releases, but with no test case to look at it's hard
to be sure about that. Widening the counts seems a good future-proofing
measure in any event.)

Modified Files:
--------------
pgsql/src/include/storage:
lock.h (r1.113 -> r1.114)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h?r1=1.113&r2=1.114)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-09-16 01:56:35 pgsql: Widen the nLocks counts in local lock tables from int to int64.
Previous Message User Fxjr 2008-09-16 01:02:40 npgsql - Npgsql2: [#1010474] Savepoint support is missing.