pgsql: Fix using too many LWLocks bug, reported by Craig Ringer

From: teodor(at)postgresql(dot)org (Teodor Sigaev)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix using too many LWLocks bug, reported by Craig Ringer
Date: 2008-04-22 17:52:43
Message-ID: 20080422175243.DDB227559CC@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix using too many LWLocks bug, reported by Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au>.
It was my mistake, I missed limitation of number of held locks, now GIN doesn't
use continiuous locks, but still hold buffers pinned to prevent interference
with vacuum's deletion algorithm.

Backpatch is needed.

Modified Files:
--------------
pgsql/src/backend/access/gin:
ginget.c (r1.13 -> r1.14)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.13&r2=1.14)
pgsql/src/include/access:
gin.h (r1.17 -> r1.18)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.17&r2=1.18)

Browse pgsql-committers by date

  From Date Subject
Next Message Teodor Sigaev 2008-04-22 17:53:41 pgsql: Fix using too many LWLocks bug, reported by Craig Ringer
Previous Message User Dim 2008-04-22 13:46:04 prefix - prefix: Documentation proof-reading by Alvaro