Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2s0y-006vfA-Fy for pgsql-hackers@arkaria.postgresql.org; Fri, 03 May 2024 12:27:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s2s0v-008pPs-Tr for pgsql-hackers@arkaria.postgresql.org; Fri, 03 May 2024 12:27:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2s0v-008pPk-K1 for pgsql-hackers@lists.postgresql.org; Fri, 03 May 2024 12:27:46 +0000 Received: from fhigh2-smtp.messagingengine.com ([103.168.172.153]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2s0t-001LC4-Mu for pgsql-hackers@postgresql.org; Fri, 03 May 2024 12:27:45 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 785CC114005F; Fri, 3 May 2024 08:27:42 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 03 May 2024 08:27:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm2; t=1714739262; x=1714825662; bh=7AXqrotQjL463VrstTmAuGbZ/fvFVPIS lWmf0Y92jx0=; b=fnDwhbtdPEQYfK79YJZfyEDO1GtzXOBWLoZov3baqnxLJjMR 2JPBMmuAXJcrZ+3MSs+LjCdinhqkwvyImN20V4gYgyyL2THe4Sh80ONVN7n7HvYB gVY2Zw8GFQHusj/z2dXioua+ItXF+cIErgnzDiw/2pgrxzP1YaeD+9BOItUOY+lE nJy/9DGQzNMggeRxFsAvVzyMX41rjhkMJ6E1IlaJNSKh8ei9zAownmrM4D9Hje2J I5Bci37QBOSb936b+D3yvVHlhK49jUbchWy8/K7vk6XMyWRua1hrjTfZAKkgGreE 67bd9AZGki2mmytDWhYFsmvzG4HgspCPQern/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714739262; x= 1714825662; bh=7AXqrotQjL463VrstTmAuGbZ/fvFVPISlWmf0Y92jx0=; b=B oI3+wF2Q2fIRxP5B1B+lR3fyBKolzeU4Amgx5iAvLXDsr0d4hdpn1R0Sqk/fgntF +BpQwuVV/duaBfGiyNhsqGvxe/F3He4ga5fWZg6ddHFbPkoVZu7tIobYa9vGA1VD iwN7kKJMRR8/jwOm3IbXedqxpIGEWN5Vg8wxpBkoeY3FpH8scMl25lc4vmjFcK4D UjSt51BUxN0B7vqRMUjz+wCmssdi3xDr8GbDZntDFv9ljyduYJTGj55My+sHsoBp rWiEFI31M6OtEhfRctqwR9vwxgQ0T1Z142vhCvZmeDTfu+X6sQ9BUKSHy8AfV58q C5t0AQwnt+POiaZqO7UGQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvtddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepgfejtdfhkeeftdeugfeileehteeljeeghfeuledthfeu tedvffdukeefjefhgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 May 2024 08:27:41 -0400 (EDT) Message-ID: <07982fd7-e9a8-4aff-aa02-efcb0dd6402f@eisentraut.org> Date: Fri, 3 May 2024 14:27:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: A failure in prepared_xacts test To: Tom Lane , Michael Paquier Cc: Richard Guo , PostgreSQL-development References: <1068977.1714367460@sss.pgh.pa.us> Content-Language: en-US From: Peter Eisentraut In-Reply-To: <1068977.1714367460@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 29.04.24 07:11, Tom Lane wrote: > Up to now, we've only worried about whether tests running in parallel > within a single test suite can interact. It's quite scary to think > that the meson setup has expanded the possibility of interactions > to our entire source tree. Maybe that was a bad idea and we should > fix the meson infrastructure to not do that. I fear that otherwise, > we'll get bit regularly by very-low-probability bugs of this kind. I don't think there is anything fundamentally different in the parallelism setups of the make-based and the meson-based tests. There are just different implementation details that might affect the likely orderings and groupings.