On 03/26/2013 11:30 PM, Tom Lane wrote: > Stefan Kaltenbrunner <ste...@kaltenbrunner.cc> writes: >> hmm - will look into that in a bit - but I also just noticed that on the >> same day spoonbill broke there was also a commit to that file >> immediately before that code adding the fflush() calls. > > It's hard to see how those would be related to this symptom. My bet > is that the new fk-deadlock test exposed some pre-existing issue in > isolationtester. Not quite clear what yet, though.
yeah removing them does not seem to change the behaviour at all > > A different line of thought is that the cancel was received by the > backend but didn't succeed in cancelling the query for some reason. I added the "pgcancel failed" codepath you suggested but it does not seem to get triggered at all so the above might actually be what is happening... Stefan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
