Re: Possible causes for "tuple concurrently updated" error - Mailing list pgsql-general

From Jacob Scott
Subject Re: Possible causes for "tuple concurrently updated" error
Date
Msg-id CA+yM-qY7GPAoCOs=25Vcm04oksiibj6LjLjtYsZmpfRwMDuqqg@mail.gmail.com
Whole thread Raw
In response to Re: Possible causes for "tuple concurrently updated" error  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
Pinpoint updates of the form

UPDATE $TABLE set field1=$FOO, field2=$BAR ... WHERE pk=$ID
  • All fields are specified
  • Table has no foreign keys (but does have a unmber of indexes)
  • executed as a prepared statement with bind params & data for multiple rows provided


On Thu, May 5, 2016 at 8:13 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Jacob Scott wrote:
> Arg, should have included this in my initial email :-(
>
> 9.3.11

OK.  So what are the updates doing?  Are there any FKs involved?

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-general by date:

Previous
From: Jacob Scott
Date:
Subject: Re: Possible causes for "tuple concurrently updated" error
Next
From: George Neuner
Date:
Subject: Re: PostgreSQL and Windows 10 exception 0xC0000018