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:54:19
Message-ID: 20080422175419.C4A9E7559CD@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.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
pgsql/src/backend/access/gin:
ginget.c (r1.10 -> r1.10.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.10&r2=1.10.2.1)
pgsql/src/include/access:
gin.h (r1.16 -> r1.16.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.16&r2=1.16.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message User Dim 2008-04-23 10:11:49 prefix - prefix: picksplit presorting avalable with
Previous Message Teodor Sigaev 2008-04-22 17:53:41 pgsql: Fix using too many LWLocks bug, reported by Craig Ringer