Re: improving speed of make check-world

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improving speed of make check-world
Date: 2015-04-28 20:05:16
Message-ID: 553FE7FC.2040707@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/28/15 9:09 AM, Michael Paquier wrote:
>> I guess by redirecting it into the log file you indicated, but is that a
>> > good idea to redirect stderr?
> I am sure that Peter did that on purpose, both approaches having
> advantages and disadvantages. Personally I don't mind looking at the
> install log file in tmp_install to see the state of the installation,
> but it is true that this change is a bit disturbing regarding the fact
> that everything was directly outputted to stderr and stdout for many
> years.

Not really. Before, pg_regress put the output of its internal make
install run into a log file. Now make is just replicating that
behavior. I would agree that that seems kind of obsolete now, because
it's really just another sub-make. So if no one disagrees, I'd just
remove the log file redirection in temp-install.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2015-04-28 20:10:42 Re: [COMMITTERS] pgsql: Add transforms feature
Previous Message Tom Lane 2015-04-28 19:59:11 Re: cache invalidation for PL/pgsql functions