aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-09-16 01:56:43 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-09-16 01:56:43 +0000
commit6d4b3f19ac64d08fe10fad6486fa2a7af7186020 (patch)
tree33e4c40b8bca75a19031007f42d8a1006d9e77b9 /src/backend/access/gist/gistvacuum.c
parent49b505fd6cc06aad35407d3896ea34019654ccaf (diff)
downloadpostgresql-6d4b3f19ac64d08fe10fad6486fa2a7af7186020.tar.gz
postgresql-6d4b3f19ac64d08fe10fad6486fa2a7af7186020.zip
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.)
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions