Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0K2H-0004Cs-11 for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jan 2021 08:00:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l0K2F-000838-02 for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jan 2021 08:00:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0K2E-000831-6P for pgsql-hackers@lists.postgresql.org; Fri, 15 Jan 2021 08:00:42 +0000 Received: from forward4-smtp.messagingengine.com ([66.111.4.238]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0K28-00076H-VS for pgsql-hackers@lists.postgresql.org; Fri, 15 Jan 2021 08:00:41 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailforward.nyi.internal (Postfix) with ESMTP id CDE7C19C3DBE; Fri, 15 Jan 2021 03:00:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 15 Jan 2021 03:00:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=909pm2zattJL3XVvRplOCDG0Vp65Yhfrk8Ah6Uz6l EM=; b=mn2BHu45c+3+bgiws8dYsu1n520A8oaf/iB7tF603n/IHsHHDHPmQ4kpL fk0N0/Twfyw0tqoN3kWmjNEm0gWGyT51R705+kcfGYQIsoTOGVAER9FFnrSQBRpg j7G0GAWU3ZHmDyPeWgZoBzBFI/x2wKWiggdJxfgO/HT6NLHnYLA2EXuwMT0JmdcW xaKiHD5NBtkOcUBpbeYONA1MKAXw4aWb18BK8Uf6HMjeBNa2t8T4GcNxxVujnbz0 I0P8MZKAtoAU803Yev1HF0oA2UK7PIPPYw6prCn+yVyPyNKjqQYZOGzz/FO7+qBR C8M9ZAqsKzhq3NqDtLGdy7vH8yRhw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtddugdduudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpefhteffhedutefgheel ffefveeihefgteettdetledvfedtieelkeffueeuteffueenucffohhmrghinhepthgvsh htrdhshhenucfkphepkeejrddujeejrdejvddrudegvdenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuth esvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p57b1488e.dip0.t-ipconnect.de [87.177.72.142]) by mail.messagingengine.com (Postfix) with ESMTPA id 6DF85108005C; Fri, 15 Jan 2021 03:00:32 -0500 (EST) Subject: Re: pg_upgrade test for binary compatibility of core data types To: Andrew Dunstan , Bruce Momjian , Justin Pryzby References: <20191015001817.zei45apgpu5dzngr@development> <20191015044118.GO3599@telsasoft.com> <20191015070725.csmdmdvrlb6klwkg@development> <20201206180248.GI24052@telsasoft.com> <20201216172222.GS30237@telsasoft.com> <20201227190729.GB26311@telsasoft.com> <20210112041352.GY1849@telsasoft.com> <20210112171559.GO4320@momjian.us> <20210112172753.GC1849@telsasoft.com> <20210112175356.GP4320@momjian.us> <66753439-83ae-7be5-6e41-9537a6041a39@dunslane.net> Cc: Tomas Vondra , Tom Lane , Andres Freund , buschmann@nidsa.net, pgsql-hackers@lists.postgresql.org, Noah Misch From: Peter Eisentraut Organization: EnterpriseDB Message-ID: Date: Fri, 15 Jan 2021 09:00:31 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <66753439-83ae-7be5-6e41-9537a6041a39@dunslane.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2021-01-12 22:44, Andrew Dunstan wrote: > Cross version pg_upgrade is tested regularly in the buildfarm, but not > using test.sh. Instead it uses the saved data repository from a previous > run of the buildfarm client for the source branch, and tries to upgrade > that to the target branch. Does it maintain a set of fixups similar to what is in test.sh? Are those two sets the same?