Re: random failing builds on spoonbill - backends not exiting...

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: random failing builds on spoonbill - backends not exiting...
Date: 2012-06-22 19:09:56
Message-ID: 4FE4C304.3030605@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/22/2012 08:34 PM, Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> It has now happened at least twice that builds on spponbill started to
>> fail after it failed during ECPGcheck:
>> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-06-19%2023%3A00%3A04
>> the first failure was:
>> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-05-24%2023%3A00%3A05
>> so in both cases the postmaster was not shuting down properly
>
> panther has been showing similar postmaster-does-not-shut-down failures
> every so often, though IIRC always in the IsolationCheck step not ECPG.

hmm

>
>> I did some further investiagations with robert on IM but I don't think
>> he has any further ideas other than that I have a weird OS :)
>> It seems worth noticing that this is OpenBSD 5.1 on Sparc64 which has a
>> new threading implementation compared to older OpenBSD versions.
>
> But we don't use threading ...
>
> Still, panther is NetBSD so there may be some general BSD flavor to
> whatever's going on here.

yeah the threading reference was mostly because all backtraces contain
references to threading libs and because the threading tests are the
last ones done by the ECPG changes...

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-06-22 19:30:59 Re: Catalog/Metadata consistency during changeset extraction from wal
Previous Message Andres Freund 2012-06-22 18:57:25 Re: random failing builds on spoonbill - backends not exiting...