From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | attempted to lock invisible tuple - PG 8.4.1 |
Date: | 2009-10-05 06:58:26 |
Message-ID: | 6bc73d4c0910042358k3d1adff3qa36f8df75198ecea@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm running our products test suite against PostgreSQL 8.4.1. The test
suite runs fine against 8.3.7.
With 8.4.1, some of our tests are failing with the exception
'attempted to lock invisible tuple'. The failures are repeatable -
they crash every time at the same point. They crash no matter if they
are being run in isolation or as part of the larger test suite.
Anyone know what we could be doing that triggers that? Looking at our
statement logs we don't seem to be doing anything unusual. The failing
tests I've checked are running under SERIALIZABLE isolation level, and
the database will have been recreated a few instants ago using
'createdb --template test_template_db'.
One of the statement logs is at http://paste.ubuntu.com/285983/ - I
can't see anything unusual
going on but it might help diagnose the problem.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wollny | 2009-10-05 08:13:40 | Re: Postgres won't start. Nothing in the log. |
Previous Message | Tim Uckun | 2009-10-05 04:39:17 | Postgres won't start. Nothing in the log. |