From: | Jacob Scott <jacob(dot)scott(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Possible causes for "tuple concurrently updated" error |
Date: | 2016-05-05 15:04:55 |
Message-ID: | CA+yM-qbBreoZ=XK7cZSSzzpxMy506-EjaJ5RcFA+E+CFFpTzCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Arg, should have included this in my initial email :-(
9.3.11
On Thu, May 5, 2016 at 7:46 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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
> > 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 of queries can conflict to cause this
> > error.
>
> What Postgres version are you running?
>
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-05-05 15:13:02 | Re: Possible causes for "tuple concurrently updated" error |
Previous Message | Alvaro Herrera | 2016-05-05 14:46:17 | Re: Possible causes for "tuple concurrently updated" error |