Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YMoej-0008V4-FS for pgsql-hackers@arkaria.postgresql.org; Sun, 15 Feb 2015 02:09:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YMoei-00076V-Qy for pgsql-hackers@arkaria.postgresql.org; Sun, 15 Feb 2015 02:09:56 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YMoeh-00076O-GN for pgsql-hackers@postgresql.org; Sun, 15 Feb 2015 02:09:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YMoeZ-0000dw-AY for pgsql-hackers@postgresql.org; Sun, 15 Feb 2015 02:09:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t1F29d9Y019188; Sat, 14 Feb 2015 21:09:39 -0500 From: Tom Lane To: Peter Eisentraut cc: pgsql-hackers , Fabien COELHO Subject: Re: improving speed of make check-world In-reply-to: <54DFFE0C.4060100@gmx.net> References: <53ED9E6C.1080700@gmx.net> <54DFFE0C.4060100@gmx.net> Comments: In-reply-to Peter Eisentraut message dated "Sat, 14 Feb 2015 21:01:48 -0500" Date: Sat, 14 Feb 2015 21:09:39 -0500 Message-ID: <19187.1423966179@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Peter Eisentraut writes: > On 8/31/14 5:36 AM, Fabien COELHO wrote: >> Running "make -j2 check-world" does not work because "initdb" is not >> found by "pg_regress". but "make -j1 check-world" does work fine. It >> seems that some dependencies might be missing and there is a race >> condition between temporary install and running some checks?? Maybe it >> is not expected to work anyway? See below suggestions to make it work. > Here is an updated patch that fixes this problem. Doesn't the Windows side of the house still depend on that functionality you removed from pg_regress? Perhaps that's not a big deal to fix, but it seems like a commit-blocker from here. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers