From: | "Euler Taveira de Oliveira" <eulerto(at)yahoo(dot)com(dot)br> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2166: attempted to update invisible tuple |
Date: | 2006-01-12 00:16:16 |
Message-ID: | 20060112001616.81B29F0A32@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2166
Logged by: Euler Taveira de Oliveira
Email address: eulerto(at)yahoo(dot)com(dot)br
PostgreSQL version: 8.1+
Operating system: Slackware 10.1
Description: attempted to update invisible tuple
Details:
I just execute the same transaction in 2 different backends and I got the
message: 'attempted to update invisible tuple'. In the first transaction I
execute: BEGIN - UPDATE and then open the other transaction and execute:
BEGIN - UPDATE so I commit the first one. In 8.0 it executes fine.
========== first transaction =========================
tst=# begin;
BEGIN
tst=# update produtos set estoque = estoque - itensmov.qtde from itensmov
where trim(itensmov.codigo) = 'C0001' and itensmov.fk_produto =
produtos.id_produto and produtos.controlarestoque = 'S';
UPDATE 21
tst=# commit;
COMMIT
tst=#
========== first transaction =========================
========== second transaction ========================
tst=# begin;
BEGIN
tst=# update produtos set estoque = estoque - itensmov.qtde from itensmov
where trim(itensmov.codigo) = 'C0003' and itensmov.fk_produto =
produtos.id_produto and produtos.controlarestoque = 'S';
ERRO: attempted to update invisible tuple
tst=#
========== second transaction ========================
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-12 04:16:56 | Re: BUG #2166: attempted to update invisible tuple |
Previous Message | Tom Lane | 2006-01-11 21:33:03 | Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol |