| 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:21:38 |
| Message-ID: | CA+yM-qY7GPAoCOs=25Vcm04oksiibj6LjLjtYsZmpfRwMDuqqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)2ndquadrant(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Neuner | 2016-05-05 16:40:19 | Re: PostgreSQL and Windows 10 exception 0xC0000018 |
| Previous Message | Alvaro Herrera | 2016-05-05 15:13:02 | Re: Possible causes for "tuple concurrently updated" error |