Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state
Date
Msg-id 28235.1296083758@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state  (Jan Urbański <wulczer@wulczer.org>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On ons, 2011-01-26 at 17:47 -0500, Tom Lane wrote:
>> I was a bit disturbed by the fact that fixing only one of the four
>> variant files was enough to turn the whole buildfarm green.  Are the
>> other three cases even needed anymore?  If so, how can we get some
>> coverage on them?

> This is explained in plpython/expected/README.  As you can see there, it
> would need some careful attention from buildfarm code and participants
> to cover all that.

Hmmm ... well, the fact that we have zero coverage on the first two
variants definitely seems surprising and scary to me.  Why aren't those
getting hit by the non-C-locale buildfarm runs?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Query Optimizer + Parallel Operators
Next
From: Jan Urbański
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state