Re: parallel regression test output - Mailing list pgsql-hackers

From Tom Lane
Subject Re: parallel regression test output
Date
Msg-id 13913.1263770734@sss.pgh.pa.us
Whole thread Raw
In response to Re: parallel regression test output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> This is not actually going to work nicely in cases such as the number of
> parallel tests being limited by max_connections.

Er, no, I take that back: I was thinking that the status() function
included checking of the output file, but it only prints the test name.

Still, I'm not convinced this is an improvement.  The current behavior
gives some feedback about how the set of parallel tests is progressing,
while what you suggest would typically just print all the test names
right away and then sit there for a long time.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch: Remove gcc dependency in definition of inline functions
Next
From: Tom Lane
Date:
Subject: Re: is this a bug?