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 1rMNJX-004GkW-8s for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Jan 2024 07:11:20 +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 1rMNJW-00ECrn-23 for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Jan 2024 07:11:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMNJU-00ECre-Gi for pgsql-hackers@lists.postgresql.org; Sun, 07 Jan 2024 07:11:17 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMNJO-000I76-TN for pgsql-hackers@lists.postgresql.org; Sun, 07 Jan 2024 07:11:15 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 777BD5C00A5; Sun, 7 Jan 2024 02:11:09 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 07 Jan 2024 02:11:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc: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=1704611469; x=1704697869; bh=LDHMD9hZBE gtqmZl3RJu7cfa6qO2NvYY+/hG0GxrwRg=; b=2LX0dr6UhXzWWKJc1NjP2f/mvO H8WJvyDvJ9flmvki2/CVHIvKP54CofgL1PE8K/+IS1WGUK9xDqHrt1ZlHpQacC/V vNmkUQbD1SRbrHN9mVxZiwVSnwG7G7+QeDHGzprFJJGpS5x5N5dHIQvFMDkgB8D2 ccG6aZgXSn/C7D7mTF5vZd2IiFB5hnDcs2wHJdrhjPVw0EwMGQn0d/5zfvBKkm1e 51IX25oq5lUZFNtf4WXu/4lWeD1Ra/FooO5q8bJJbVzCOrp0gjA1tPDpquTpcJN+ KOVYMx+inKmbpVzQtcOH2pq+d+/YN+ps+n/lrC6iOSYtgbTYckzfg0hU/gTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc: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= fm2; t=1704611469; x=1704697869; bh=LDHMD9hZBEgtqmZl3RJu7cfa6qO2 NvYY+/hG0GxrwRg=; b=uLULuGNt6sJUAfpEBX1bJ2lPX29hK5of/679O19KH6Gv gOeTnGW3NnzwK4pVsB1/VmnAgDFjqLxSwF/qxuRkSM22heqlL7ZMcpq68ulnp9Fu IB+BsGI0ljkdd94IMxWdfuqII+pL4c8uV4gVoiHEvvDoi/Ic0pJm2p/gYBXYO2aB bmr1XmLO9KhWpmQHeKCvn4S9wTwaHYpX8NLoVbAGl8eXAtcgdAyyc01oPCYxXtqF lxhpyWR/CqDmZqpPwUQlxlO22anCdP9PrRlETbTl3hghf9I/xKFf+r8iLcipXfXo cUUCmCyiCPKeLwJ0Am7lDLfUFx35DUrhgqc4IPadKQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehvddguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enfghrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreer tddtudenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlse hprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpefghfelfedvhefgieeghedu tedtjeeugfeltdehfedtfeetleelgfejgeehgffggfenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 7 Jan 2024 02:11:06 -0500 (EST) Date: Sun, 7 Jan 2024 16:10:50 +0900 From: Michael Paquier To: Alexander Lakhin Cc: Tom Lane , Euler Taveira , Bharath Rupireddy , Kyotaro Horiguchi , Alvaro Herrera , Andrew Dunstan , pgsql-hackers@lists.postgresql.org, Andres Freund , Bertrand Drouvot Subject: Re: Add a perl function in Cluster.pm to generate WAL Message-ID: References: <3a6978d6-e4fc-4014-b5f7-45db53d8fa53@app.fastmail.com> <5d160064-8cbe-4b32-9c55-c983b1f63b12@app.fastmail.com> <370894.1704325169@sss.pgh.pa.us> <2e203472-72b5-1b55-377a-824c3f28b190@gmail.com> <2d39b5fa-ba90-48c8-4cde-ecba4a62fa3b@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="g7zDvfquhOLSxU4O" Content-Disposition: inline In-Reply-To: <2d39b5fa-ba90-48c8-4cde-ecba4a62fa3b@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --g7zDvfquhOLSxU4O Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 05, 2024 at 11:00:00PM +0300, Alexander Lakhin wrote: > Your suspicion was proved right. After > git show c161ab74f src/test/recovery/t/035_standby_logical_decoding.pl=A0= | git apply -R > 20 iterations with 20 tests in parallel performed successfully for me > (twice). >=20 > So it looks like c161ab74f really made the things worse. We have two different failures here, one when VACUUM fails for a shared relation: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2024-0= 1-03%2017%3A09%3A27 https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2024-0= 1-01%2020%3A10%3A18 And the second failure happens for VACUUM FULL with a shared relation: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2024-0= 1-03%2020%3A07%3A15 In the second case, the VACUUM FULL happens *BEFORE* the new advance_wal(), making c161ab74f unrelated, no? Anyway, if one looks at the buildfarm logs, this failure is more ancient than c161ab74f. We have many of them before that, some reported back in October: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2023-1= 0-19%2000%3A44%3A58 https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2023-1= 0-30%2013%3A39%3A20 I suspect on the contrary that c161ab74f may be actually helping here, because we've switched the CREATE TABLE/INSERT queries to not use a snapshot anymore, reducing the reasons why a slot conflict would happen? Or maybe that's just a matter of luck because the test is racy anyway. Anyway, this has the smell of a legit bug to me. I am also a bit dubious about the choice of pg_authid as shared catalog to choose for the slot invalidation check. Isn't that potentially racy with the scans we may do on it at connection startup? Something else should be chosen, like pg_shdescription as it is non-critical? I am adding in CC Bertrand and Andres, as author and committer behind befcd77d53217b. -- Michael --g7zDvfquhOLSxU4O Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmWaTnoACgkQnvQgOdby QH2c5A/8DO+2TbwjgJ0BrLGDNSe1NJ2CQS5cemh5jPWEV4Jz2OoZCx9UBjJiN3N/ 6mI72BoROa/Qnv3q0JsVzFKATW2uxR6xtMTaq29o3/gzAvCb4PthlhV5qocWqP6L F42lgHhRbsRPbEz/xcu4FBDM/AHtwGJfYIDsGPyDQGCxp52VL8eB2KGKbPX2kLUG q2zkZRK71EAsXZba9EtIBp+P43jk7dNJ4PfwHC9GJtB+fKOgDkd7czL4SCSx7UcA 6vR3/7gzEI4x9xmXoeUE7JRZxftM9F5P254sxS6DHu2FLq/TMLL4/xxrn5vB68QN w6jOISFT7zBQG+s24oFqn9qx+ge85EbqG4xIJM6QS/m2abU6Bq/vUPbnV6M4WFuK 5/sVkSPM5CCjzizOkQne2v56YmEWmwDRWFdr3Cr1ds118pdU9iuTlU5sI9/ApdIl IBQI+hfrdLohM4suem/Z5D/azNZDoW5ful919mE/ppwQlS48tkmHbFJvHniL+sAI BK9OaSkDua+PozW6oZXy12jfPArjLhanPbeOxgpoi2q1oRDiu7FvhjZcIduzLR2b cniDzXqJ1OW5IMnHEqfQGUD+6qd3DoAdxTc+6cYWWkryj8PBYV8MzALAA8IU5+GD YTrho5cnKz+K9FEDLY6uZNxR/rCc01jSsDa2tAt7uq/oWqzZFF0= =i0OL -----END PGP SIGNATURE----- --g7zDvfquhOLSxU4O--