pgsql: Widen the nLocks counts in local lock tables from int to int64. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Widen the nLocks counts in local lock tables from int to int64.
Date
Msg-id 20080916015643.A182E7545A4@cvs.postgresql.org
Whole thread Raw
List 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.)

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/include/storage:
        lock.h (r1.102 -> r1.102.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h?r1=1.102&r2=1.102.2.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Widen the nLocks counts in local lock tables from int to int64.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Widen the nLocks counts in local lock tables from int to int64.