pgsql: Fix using too many LWLocks bug, reported by Craig Ringer - Mailing list pgsql-committers

From teodor@postgresql.org (Teodor Sigaev)
Subject pgsql: Fix using too many LWLocks bug, reported by Craig Ringer
Date
Msg-id 20080422175243.DDB227559CC@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix using too many LWLocks bug, reported by Craig Ringer
<craig@postnewspapers.com.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)

pgsql-committers by date:

Previous
From: dim@pgfoundry.org (User Dim)
Date:
Subject: prefix - prefix: Documentation proof-reading by Alvaro
Next
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Fix using too many LWLocks bug, reported by Craig Ringer