On Tue, Nov 26, 2013 at 8:19 PM, Peter Geoghegan <p...@heroku.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
