Re: attempted to lock invisible tuple - PG 8.4.1

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Stuart Bishop <stuart(at)stuartbishop(dot)net>
Cc: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: attempted to lock invisible tuple - PG 8.4.1
Date: 2009-10-06 16:12:56
Message-ID: 20091006161256.GJ5929@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera wrote:
> Stuart Bishop wrote:

> > The test case (invisible.sh) and required dump (foodump.sql - 60k) are
> > at http://www.stuartbishop.net/invisible/
>
> Got it, thanks, looking.

Here's a slightly smaller test case; basically I removed the tsearch2
cruft and extra columns in the table. One thing of note is that if the
COPY commands is reduced to occupy less than one page in the target
table, the problem does not occur.

To reproduce, restore the attached file and run
BEGIN;
SET transaction_isolation TO SERIALIZABLE;
UPDATE Bug2 SET name='foobar' WHERE id=1;
ABORT;

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

Attachment Content-Type Size
foodump2.sql text/plain 11.8 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Fetter 2009-10-06 16:18:22 Re: Wishlist of PL/Perl Enhancements for PostgreSQL 8.5
Previous Message Alan McKay 2009-10-06 15:25:31 LF PostgreSQL virtual Linux host provider in India and/or Asia Pac