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:53:41 |
Message-ID: | 20080422175341.B963A7559CC@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_2_STABLE
Modified Files:
--------------
pgsql/src/backend/access/gin:
ginget.c (r1.4.2.1 -> r1.4.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.4.2.1&r2=1.4.2.2)
pgsql/src/include/access:
gin.h (r1.9.2.1 -> r1.9.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.9.2.1&r2=1.9.2.2)
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2008-04-22 17:54:19 | pgsql: Fix using too many LWLocks bug, reported by Craig Ringer |
Previous Message | Teodor Sigaev | 2008-04-22 17:52:43 | pgsql: Fix using too many LWLocks bug, reported by Craig Ringer |