Arg, should have included this in my initial email :-(
9.3.11
On Thu, May 5, 2016 at 7:46 AM, Alvaro Herrera
wrote:
> On Wed, May 04, 2016 at 11:52:47PM -0700, Jacob Scott wrote:
> > Hi,
> >
> > I'm seeing a "tuple concurrently updated" error thrown while executing
>
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,
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 Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent
On Wed, May 04, 2016 at 11:52:47PM -0700, Jacob Scott wrote:
> Hi,
>
> I'm seeing a "tuple concurrently updated" error thrown while executing
> UPDATE statements. I've attempted to diligently review previous threads on
> this error (e.g.,
>
Hi,
I'm seeing a "tuple concurrently updated" error thrown while executing
UPDATE statements. I've attempted to diligently review previous threads on
this error (e.g.,
https://www.google.com/webhp?ie=UTF-8#q=tuple+concurrently+updated+update+site:postgresql.org)
but am confused about what classes