Skip site navigation (1) Skip section navigation (2)

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:35
Message-ID: 20080916015635.66B147545A4@cvs.postgresql.org (view raw or flat)
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.)

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/src/include/storage:
        lock.h (r1.112 -> r1.112.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h?r1=1.112&r2=1.112.2.1)

pgsql-committers by date

Next:From: Tom LaneDate: 2008-09-16 01:56:43
Subject: pgsql: Widen the nLocks counts in local lock tables from int to int64.
Previous:From: Tom LaneDate: 2008-09-16 01:56:26
Subject: pgsql: Widen the nLocks counts in local lock tables from int to int64.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group