On Mon, Jan 18, 2010 at 4:54 PM, Peter Eisentraut wrote:
> On sön, 2010-01-17 at 23:54 -0500, Robert Haas wrote:
>> I always assumed that it was printing the names as the tests finished,
>> probably because of the way the output is staggered. If they were
>> printed when the tests were started, t
On sön, 2010-01-17 at 23:54 -0500, Robert Haas wrote:
> I always assumed that it was printing the names as the tests finished,
> probably because of the way the output is staggered. If they were
> printed when the tests were started, the list would be printed all but
> simultaneously.
Well, as lo
On Sun, Jan 17, 2010 at 3:19 PM, Peter Eisentraut wrote:
> There is something slightly funny about the regression test output.
> When it starts a parallel group, it prints something like
>
> parallel group (14 tests): select_views portals_p2 rules foreign_key
> cluster dependency guc bitmapops co
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 convinc
Peter Eisentraut writes:
> I propose to adjust the behavior so that the "parallel group" line
> prints the test names before/as the tests are started, and then the
> subsequent lines print the results after the tests finish, as is
> currently the case.
This is not actually going to work nicely in
There is something slightly funny about the regression test output.
When it starts a parallel group, it prints something like
parallel group (14 tests): select_views portals_p2 rules foreign_key
cluster dependency guc bitmapops combocid tsearch tsdicts foreign_data
window xmlmap
One would think
