| 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 17:36:14 |
| Message-ID: | 20091006173614.GO5929@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Filip Rembiałkowski | 2009-10-06 17:41:26 | Re: Wishlist of PL/Perl Enhancements for PostgreSQL 8.5 |
| Previous Message | Alvaro Herrera | 2009-10-06 17:21:36 | Re: attempted to lock invisible tuple - PG 8.4.1 |