Re: attempted to lock invisible tuple - PG 8.4.1 - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: attempted to lock invisible tuple - PG 8.4.1
Date
Msg-id 20091006173614.GO5929@alvh.no-ip.org
Whole thread Raw
In response to Re: attempted to lock invisible tuple - PG 8.4.1  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
Alvaro Herrera wrote:

> create trigger onetest_t before update on onetest for each row
>         execute procedure upd();
>
> insert into onetest select a, repeat('xyzxz', 100), 'new' from generate_series(1, 50) a;
>
> BEGIN;
> SET transaction isolation level SERIALIZABLE;
> UPDATE onetest SET description = 'no no', id = 1 where id = 1;
> commit;

What I don't understand is why this works when the update uses the same
target page.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: attempted to lock invisible tuple - PG 8.4.1
Next
From: Filip Rembiałkowski
Date:
Subject: Re: Wishlist of PL/Perl Enhancements for PostgreSQL 8.5