Re: spoonbill vs. -HEAD - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: spoonbill vs. -HEAD
Date
Msg-id 51534066.10203@kaltenbrunner.cc
Whole thread Raw
In response to Re: spoonbill vs. -HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: spoonbill vs. -HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 03/26/2013 11:30 PM, Tom Lane wrote:
> Stefan Kaltenbrunner <stefan@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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Next
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: Allow external recovery_config_directory