Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hALq6-00063L-OS for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Mar 2019 21:48:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hALq4-0006GW-7c for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Mar 2019 21:48:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hALq3-0006GP-VP for pgsql-hackers@lists.postgresql.org; Sat, 30 Mar 2019 21:48:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hALq1-00012m-Jr for pgsql-hackers@postgresql.org; Sat, 30 Mar 2019 21:48:31 +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 x2ULmQ27009042; Sat, 30 Mar 2019 17:48:26 -0400 From: Tom Lane To: Andrew Dunstan cc: PostgreSQL-development Subject: Re: Teach pg_upgrade test to honor NO_TEMP_INSTALL In-reply-to: <5506b8fa-7dad-8483-053c-7ca7ef04f01a@2ndQuadrant.com> References: <5506b8fa-7dad-8483-053c-7ca7ef04f01a@2ndQuadrant.com> Comments: In-reply-to Andrew Dunstan message dated "Sat, 30 Mar 2019 16:42:16 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9040.1553982506.1@sss.pgh.pa.us> Date: Sat, 30 Mar 2019 17:48:26 -0400 Message-ID: <9041.1553982506@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andrew Dunstan writes: > On some machines (*cough* Mingw *cough*) installs are very slow. We've > ameliorated this by allowing temp installs to be reused, but the > pg_upgrade Makefile never got the message. Here's a patch that does > that. I'd like to backpatch it, at least to 9.5 where we switched the > pg_upgrade location. The risk seems appropriately low and it only > affects our test regime. I haven't tested this, but it looks reasonable. I suspect you need double-quotes around the path values, as in the adjacent usage of EXTRA_REGRESS_OPTS. regards, tom lane