| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Date: | 2013-11-27 09:09:49 |
| Message-ID: | CAM3SWZS2--GOvUmYA2ks_aNyfesb0_H6T95_k8+wyx7Pi=CQvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 26, 2013 at 8:19 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> There are some visibility-related race conditions even still
I also see this, sandwiched between the very many "deadlock detected"
errors recorded over 6 or so hours (this is in chronological order,
with no ERRORs omitted within the range shown):
ERROR: deadlock detected
ERROR: deadlock detected
ERROR: deadlock detected
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: unable to fetch updated version of tuple
ERROR: deadlock detected
ERROR: deadlock detected
ERROR: deadlock detected
ERROR: deadlock detected
This, along with the already-discussed "attempted to update invisible
tuple" forms a full account of unexpected ERRORs seen during the
extended run of the test case, so far.
Since it took me a relatively long time to recreate this, it may not
be trivial to do so. Unless you don't think it's useful to do so, I'm
going to give this test a full 24 hours, just in case it shows up
anything else like this.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2013-11-27 09:14:00 | Re: [GENERAL] pg_upgrade ?deficiency |
| Previous Message | Andres Freund | 2013-11-27 09:02:02 | Re: Platform-dependent(?) failure in timeout handling |