Hi all,
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively. The user managed to isolate the
problem and SQL generating the problem. A few sessions are required to
generate the error.
T1:
---
begin;
listen test;
commit;
T2:
---
begin;
Gavin Sherry [EMAIL PROTECTED] writes:
ERROR: tuple concurrently updated
A brief look into this:
heap_update() in T3 (called by AtCommit_Notify()) calls
HeapTupleSatisfiesUpdate(). This returns HeapTupleBeingUpdated. Once we
issue COMMIT; in T1 updates pg_listen and the tuple T3 is trying
Gavin Sherry [EMAIL PROTECTED] writes:
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively.
I've applied a fix for this to CVS tip.
Thinking about the implications of rolling back UNLISTEN, it occurs to
me that there is another possible
On Mon, 15 Sep 2003, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively.
I've applied a fix for this to CVS tip.
Great.
I think that whenever we get around to rewriting
