Re: simple_heap_update: tuple concurrently updated -- during INSERT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: simple_heap_update: tuple concurrently updated -- during INSERT
Date
Msg-id 26183.1086799131@sss.pgh.pa.us
Whole thread Raw
In response to simple_heap_update: tuple concurrently updated -- during INSERT  ("SZŰCS Gábor" <surrano@mailbox.hu>)
List pgsql-hackers
"SZŰCS Gábor" <surrano@mailbox.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


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Tablespaces
Next
From: Alvaro Herrera
Date:
Subject: Re: Frequently updated tables