Re: strange buildfarm failures

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange buildfarm failures
Date: 2007-05-02 17:44:12
Message-ID: 87irbb6ryr.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> Nailed it -- this is the actual bug that causes the abort. But I am
>> surprised that it doesn't print the error message in Stefan machine's;
>
> Hm, maybe we need an fflush(stderr) in ExceptionalCondition?

stderr is supposed to be line-buffered by default. Couldn't hurt I suppose.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2007-05-02 17:52:18 Re: Sequential scans
Previous Message Magnus Hagander 2007-05-02 17:37:14 Re: Feature freeze progress report