From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Creager <robert(at)logicalchaos(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: build farm machine using <make -j 8> mixed results |
Date: | 2012-09-09 07:29:02 |
Message-ID: | 14952.1347175742@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On Sat, 2012-09-08 at 19:54 -0400, Tom Lane wrote:
>> Anyway, what I notice is that I get different types of failures, but
>> they are all under ecpg/. What I think we need to do is insert
>> .NOTPARALLEL in ecpg/Makefile,
> I'd hate that, because the ecpg build is one of the slowest parts of the
> build, so de-parallelizing it would slow down everything quite a bit.
There's only one bit of it that's slow, which is the bison build +
preproc.c compile, which is necessarily serial anyway. So I think
trying to avoid .NOTPARALLEL there is a complete waste of effort.
But if you wanna fix it some other way, step right up.
(This all does remind me of the "Recursive Make Considered Harmful"
thread from awhile back. Is anyone prepared to go down that path
now? I'm not terribly excited by that, as yet --- yeah, it would
be better, but the work involved seems out of proportion to the
benefit.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-09-09 07:35:05 | Re: Supporting plpython 2+3 builds better |
Previous Message | Gezeala M. Bacuño II | 2012-09-09 05:59:07 | Re: [BUGS] BUG #7521: Cannot disable WAL log while using pg_dump |