From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | 'Too many LWLocks held' with GIN pg_trgm_ops index [RE-SENT] |
Date: | 2008-04-21 08:15:41 |
Message-ID: | 480C4D2D.80601@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
[RESENT MESSAGE - the previous one was presumably held for moderation
because of an attachment. If the prior one did in fact make it through
and I just didn't get it then sorry for the noise.]
Hi all
Following my -general post about this issue I'm supplying a test case
for a query that fails with a 'Too many LWLocks held' error.
The test data, system configuration details, etc are in the tarball that
you can obtain here:
http://www.postnewspapers.com.au/~craig/lwlock_test.tar.bz2
The README in the package provides all the detail I can think of, but
here's the summary again:
------
This is a test case for a `Too many LWLocks held' error encountered when
using pg_trgm with a GIN index in the following query:
SELECT a.message, b.message FROM po_message a, po_message b
WHERE a.id <> b.id AND a.message % b.message;
The error does not occur if a GIST index is present on
`po_message.message' instead of a GIST index, or if no index is present
at all. It only arises when the % operator is used.
------
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Prischepa Vladimir | 2008-04-21 11:15:23 | pg_dump error when dumping mixed-case name tables |
Previous Message | Buk | 2008-04-21 01:58:45 | BUG #4119: Add foreign key fails for non-presence of a record that does exist. |