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 1rLXSD-008Wn8-9E for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Jan 2024 23:48:49 +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 1rLXSB-00GJOG-MF for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Jan 2024 23:48:47 +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 1rLXSB-00GJO8-Cl for pgsql-hackers@lists.postgresql.org; Thu, 04 Jan 2024 23:48:47 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rLXS8-00Dlt4-Ld for pgsql-hackers@lists.postgresql.org; Thu, 04 Jan 2024 23:48:46 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1AE6C5C0235; Thu, 4 Jan 2024 18:48:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 04 Jan 2024 18:48:44 -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=1704412124; x=1704498524; bh=TB82qAlNlv otElrVRBe1fog7mS9G2Er5uZWPZULdSgE=; b=pUXkyVoord/HPPyvlR5LBSguZk tLfrAt7RlFNgCuwr4WAn+6u+2/ggh8IJzO67AhSjzu/VrvofgIg85CAZCXwvEQM+ kzD9h3hj8+vCELxr91Fj2TN5nHUj4yzYNvTMaJ51UgBSnM3GQhuM3F76Z45nXMAS Wdr/drmbKthlGupx2gbzPbRMV2+bkNFCilN8iZBhrOG8LRwBFckvRQ/9yBbPnhoM 9ns5hcphDKG0oXRvUYZEJ3A8p1jycpaHlHoBrph6GiPA7L4xz6v6cjKI9ZFyM1yB TbcRx/IqWAHB4/zKrE3QkK0xVSfmQQJsv//pQ5xhi2k/IwI19lnZDMwGc3GQ== 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=1704412124; x=1704498524; bh=TB82qAlNlvotElrVRBe1fog7mS9G 2Er5uZWPZULdSgE=; b=riRXIxCZLzkT34v2lN60PkojU02pWegMCzDNBMGX+pCr 1VNgbxuCbQ7Lf0aRhu99kFYzHM6dcDjm8Jrss3KbD335I4EZN7NoHNvMKNZj3y2J NLrHVl1zTr4Dh61GkYkn27RILAjnsF7l9Gqq2jCkQApMNG11IMQRfjAuT9numm0U mWPOfStS3FjIg4DeUXkxwzfmFnVLYifJ4M4uS8H5/eNqS2ZLTBlOKaL98BmEW8KN s1+bS2s20lzK9XddOsuBWOeZhPcbctb0n0KTPSIxPoj6PijSN9ZAoNPQRnUbBOgO Yl8VEwNCLAxB2ZHqDxZSRO3jUPCuXKv/hBCDi1PizA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdegkedgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddunecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepgffhleefvdehgfeigeehudet tdejuefgledtheeftdefteellefgjeeghefggffgnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 4 Jan 2024 18:48:40 -0500 (EST) Date: Fri, 5 Jan 2024 08:48:33 +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 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5leiGv02Qw3jNQWX" Content-Disposition: inline In-Reply-To: <2e203472-72b5-1b55-377a-824c3f28b190@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --5leiGv02Qw3jNQWX Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 04, 2024 at 04:00:01PM +0300, Alexander Lakhin wrote: > Reproduced here. Did you just make the run slow enough to show the failure with valgrind? > As I can see in the failure logs you referenced, the first problem is: > #=A0=A0 Failed test 'inactiveslot slot invalidation is logged with vacuum= on pg_authid' > #=A0=A0 at t/035_standby_logical_decoding.pl line 224. > It reminded me of: > https://www.postgresql.org/message-id/b2a1f7d0-7629-72c0-2da7-e9c4e336b01= 0%40gmail.com >=20 > It seems that it's not something new, and maybe that my analysis is still > valid. If so, VACUUM FREEZE/autovacuum =3D off should fix the issue. Not sure about that yet. -- Michael --5leiGv02Qw3jNQWX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmWXQ9EACgkQnvQgOdby QH2a8A/8CfNTAlfprBRF0sPl7ssAt2F6ArvFAlQR2kKvZGkQeJ32Nwrurpyf9pw/ eAtBdDSKuKQ78/s6jw8OP4bwvQoWwTcmuVsCeTH3blAN3XMAGIfIaosQJPMMNcWp aAUQr+QQ9ZZQMn44JVSpc1zjNPe6JawVzTbB4lJanInySvdm/USV/KqFsTWBmGvH BX4Q6TvSQ5gp5OGXVwaUO9lbSP0/GUINXY6jPLP/IO/sMjOAQjDGDegy2y+PYzkt jq6uK1jwxgNzs4PgzFlBzLvUO2z+H9u97Ul7eXZmSPWgstZUIVBpw9E+0OempOmt /Z0ZvV/qtNf7JcMrWyZxPvKIVABuBNN4iDmgO18H3tabR5CGXUVN11c17FHQnOF6 sJjaRdPVCHOSKevFeEvpn2BijDDH7DMJA0TRtQ7rpqCwKfouFrrQW7m1cl4vFer3 XPc4hBP5UIMmU5ZTwg99mgq/y0+nVW3Dd9HUPrXuY9DSrepUjpSgTzH+ZTCVrUTM YfW/fjRqgKdkhlWbr2SLS/kjf+FWz6HluNvZp3t2DGP0ZdP8yspuSwBJ6ALMlDQ6 8f822JuXJRZOzpUl2BGdCQ371zNIcPIT1U0uSB9NjDXWAkSvvDpVUT9R8zbbf9p9 P/X0cO7HAEyQopbUs1uQJHVwL414chhzg2Ij67I3TQKkcZ8tS7w= =D3sO -----END PGP SIGNATURE----- --5leiGv02Qw3jNQWX--