| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgresql Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: spoonbill vs. -HEAD |
| Date: | 2013-03-27 18:54:30 |
| Message-ID: | 51534066.10203@kaltenbrunner.cc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/26/2013 11:30 PM, Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-03-27 19:08:15 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
| Previous Message | Michael Paquier | 2013-03-27 18:16:23 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |