Re: parallel regression test output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: parallel regression test output
Date: 2010-01-17 23:25:34
Message-ID: 13913.1263770734@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-17 23:47:00 Re: is this a bug?
Previous Message Tom Lane 2010-01-17 23:22:27 Re: Patch: Remove gcc dependency in definition of inline functions