Re: [COMMITTERS] pgsql: Improved parallel make support

Dave Page <dpage@pgadmin.org>

From: Dave Page <dpage@pgadmin.org>

To: Peter Eisentraut <peter_e@gmx.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@postgresql.org

Date: 2010-11-14T10:30:59Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improved parallel make support
- 19e231bbdaef 9.1.0 cited

On Sat, Nov 13, 2010 at 8:13 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On lör, 2010-11-13 at 20:07 +0200, Peter Eisentraut wrote:
>> On lör, 2010-11-13 at 12:20 -0500, Tom Lane wrote:
>> > Peter Eisentraut <peter_e@gmx.net> writes:
>> > > On lör, 2010-11-13 at 11:12 -0500, Tom Lane wrote:
>> > >> It looks like all the unhappy critters are getting the same "virtual
>> > >> memory exhausted" error.  I wonder whether they are all using make
>> > >> 3.80 ...
>> >
>> > > It turns out that there is an unrelated bug in 3.80 that some Linux
>> > > distributions have patched around.  3.81 or 3.82 are OK.
>> >
>> > So what do you mean by "unrelated bug"?  Can we work around it?
>>
>> The information is fuzzy, but the problem has been reported around the
>> internet, and it appears to be related to the foreach function.  I think
>> I have an idea how to work around it, but I'll need some time.
>
> Well, it looks like $(eval) is pretty broken in 3.80, so either we
> require 3.81 or we abandon this line of thought.

3.81 might be a problem for Solaris - unless I pay for a support
contract from Oracle, I'm not going to get any updates from them,
which means I'll have to install a custom build. Now that's no biggie
for me, but it does see to raise the bar somewhat for users that might
want to build from source.


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company