Re: simple_heap_update: tuple concurrently updated -- during INSERT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: SZŰCS Gábor <surrano(at)mailbox(dot)hu>
Cc: "PGH" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: simple_heap_update: tuple concurrently updated -- during INSERT
Date: 2004-06-09 16:38:51
Message-ID: 26183.1086799131@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"=?iso-8859-2?B?U1rbQ1MgR+Fib3I=?=" <surrano(at)mailbox(dot)hu> writes:
> Q1. So is this everything that can be said -- NOTIFY calls
> simple_heap_update that is concurrently updated by a different transaction?

If that's what it is, then there's still a question: why? The notify
code has enough locking that this failure shouldn't happen. If you can
reproduce this I'd like to look into it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2004-06-09 16:49:19 Re: sequences and "addval('myseq', value)"
Previous Message SZŰCS Gábor 2004-06-09 16:12:05 Re: simple_heap_update: tuple concurrently updated -- during INSERT