Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eypD6-0001qN-UY for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 01:40:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eypD5-0006hN-Kp for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 01:40:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eypD5-0006go-9z for pgsql-hackers@lists.postgresql.org; Thu, 22 Mar 2018 01:40:07 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eypD3-0005Sp-15 for pgsql-hackers@postgresql.org; Thu, 22 Mar 2018 01:40:06 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 4E9AF1012; Wed, 21 Mar 2018 21:40:04 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 21 Mar 2018 21:40:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=E6KWWMDQSoaj7ucuYy7+jXeEgVh34pdkjcfFsfgTM1Y=; b=TPWTemUM f17c0HR9tWdX62naPV7ynIwQPYLnXUrdVZQD7U+8LGRuLgiPqkhQuFfrPKY9i/+v RM15iv1mdOEQKZZRPwNMpE/3RuomsIWGt5VvIWaOIZEJv0TBBHGvsdxWmi1JGs6W LDWX5B0Tqa1xr8zNRIPKAQp72HvbvSNC6onW8vKnD+4Oh+HzBsarS9Oot+9jxWJB z5yHue0NBIC2QjNJ2PcH9MPG6luFVEenwp+8EKsy63J9wLYzYpOwbgduvxLFgl3Y S/EkFHVFCNFnxZhSZElCDczAxpYn8e8vk3AYCjeDnvH6SjMTPf4W1JdBy3S0tm8e YBVxjr+5j34Uyg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=E6KWWMDQSoaj7ucuYy7+jXeEgVh34 pdkjcfFsfgTM1Y=; b=TBwrzjGEUDQcYAidThCmoSpU0lrAVSMyBvCgHx/vl+rwR IYbamo1tMNS8TJzMIHVhFmFozHjta54vH9mJqJuboRj3I7E1VRgUR9Xho+iGWO0X QozW4Y4DQEjRWKBAmuoxN3IBzMFTGKfoZwaEb4pUfcXXBEfPnKCAn8LdwjAwQZ8+ Kt2Pu/LnP+8PLoaL9cpJQEx8ld+4NQeE0DSzrKa3apOF5OHHdKu5MY1EDUu8vQ/w iTtg/Ul7YdLkVW5I00TtOvEwcldovLuscpUF4J0VEoK5s1mbpmn8l5nHTT8b6aDv 1kLNtgg4GGczuHFYNrWblYmArym2fd1R5GEIkXA7A== X-ME-Sender: Received: from paquier.xyz (mp76f1f929.ap.nuro.jp [118.241.249.41]) by mail.messagingengine.com (Postfix) with ESMTPA id F2D51240DC; Wed, 21 Mar 2018 21:40:00 -0400 (EDT) Date: Thu, 22 Mar 2018 10:39:57 +0900 From: Michael Paquier To: David Steele Cc: Andrew Dunstan , Tom Lane , Peter Eisentraut , Michael Paquier , Postgres hackers Subject: Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two Message-ID: <20180322013957.GD2490@paquier.xyz> References: <20180126080026.GI17847@paquier.xyz> <7d040dbb-33f3-edb7-b13d-0f4ab607af46@2ndquadrant.com> <08724398-ce66-9236-18fc-b7f22a15c017@2ndquadrant.com> <18045.1520370764@sss.pgh.pa.us> <0b59536a-2d31-7573-6505-1860d00618bd@pgmasters.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jCrbxBqMcLqd4mOl" Content-Disposition: inline In-Reply-To: <0b59536a-2d31-7573-6505-1860d00618bd@pgmasters.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --jCrbxBqMcLqd4mOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 21, 2018 at 10:51:04AM -0400, David Steele wrote: > On 3/6/18 4:12 PM, Tom Lane wrote: > It seems the consensus is that we'll need a build farm update before we > can move forward with the patch and that we don't need to wait long for > people to upgrade. >=20 > Andrew, do you have a date for the next release? Even if a lighter version of this patch stripped from multi-version support (Who uses that actually?) knowing that the buildfarm code has its own set of modules to do the same may be a good step forward as per the feedback of this thread people would like to unify the existing scripts. We could also try to figure later on how to merge the buildfarm code into upstream and if it actually makes sense or not, which is something I am not completely convinced is worth it. This would remove the need of any complicated refactoring in PostgresNode.pm to handle binary paths for a single node, at the cost of of course removing cross-upgrade checks from the tree. Still I definitely agree that a release of the buildfarm client should happen first. 9 days before the end of the commit, the window may be at the end too short for v11. -- Michael --jCrbxBqMcLqd4mOl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlqzCW0ACgkQnvQgOdby QH0zhw//QqtUE4Ol5jqW7bB9Cm6xwId3pzvWZpkIOmWrfUmKuQg1NSES9BJJ7jLO Sg67Bv8i1V8NWnuKnwdDxeo25jUFlXiuI+D3VvfSiKgvX9VLayEjB6dI08mXvZAl t4IpS7xg3UdiTz+4dkjlPr67umXsUMHQ+FNldTI8yO4e0fHrgvBW5u0WxesOYucV IJN+OPPN+R4C/odwd6GvTU3YzTYVipH/YUONkkJNMzgeFFXqSFiI1g5TsgeCWAze Jfz25VH39hhCN1tz63oyYjwbwpq34JIF2tqV3/CRjVpk58llGAZTNlrOVXh7A9ag xXg2PIvO1wTAq4FzfpFzzAvUVrOTXZaAjG1UWun0mjOCy9RmiZIZjh+dJDGKBGeI lTkjxmeXPWTLxPVs7UAkV3KOQNZ9hO5PqV9cuiGKgYHq/dY4xQxfpG9znS/+qqtX PiugzKwbtI9B8SNKA1m0ltUegDS0fL0BYme6SlA/67Yt686sxus1hDGvrfDSc+c2 exQcM6W+9w6XHb0O2motKVTUyDIUAKmNFm2rA8//WCGtFkO3pABF7pVAyTxbapRo HDxqTQrmgFocCk0Annf9uSeovzKzx6sVthfabhCpmM8cAbLjmZzdHwdkhTt82Xsh 3A0YhOsgg7PuoQgN9I/y7CKNqWO7BDZgA2Xl8RRmmpNpbkh1bak= =3b5P -----END PGP SIGNATURE----- --jCrbxBqMcLqd4mOl--