Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group