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 1sF0Pm-005ozR-IY for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Jun 2024 23:51:35 +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 1sF0Pm-00D5Xp-Bc for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Jun 2024 23:51:34 +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 1sF0Pm-00D5Xe-2f for pgsql-bugs@lists.postgresql.org; Wed, 05 Jun 2024 23:51:34 +0000 Received: from fout7-smtp.messagingengine.com ([103.168.172.150]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sF0Pf-000CLK-KF for pgsql-bugs@lists.postgresql.org; Wed, 05 Jun 2024 23:51:33 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 9835313800A2; Wed, 5 Jun 2024 19:51:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Jun 2024 19:51:25 -0400 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=fm1; t=1717631485; x=1717717885; bh=kABoX+02Io ACBJ1bLYrQWx+lYHkB0Qf9GWADQVdTAzc=; b=FVPvggxdc+gy5zSXJdquWUT5ge 3YCeqUPJz7Q6yM5xux3IBZaFt5h4rKU9/FkkRCOUEZ/Cz2bK2owItHTxnfoPYCb+ /8hvpL21SEKMq7mjDvdbpEAnj0jbAzC6OEThrs4IqPgPsbC93HV7990OEPjRf9fJ 5s5nQmHk/b4JFCcuUkyVAORAeawvE25QKW7Yw3S1TkGxw6c5BhigOhnJMWyTl25L y8q0bNRWPAUKUw7Y5C8H4TpeWv3JyJ0ZOl4T3jhLTTzoWhCC1354cqcW6CJb1rTB lcZmKXvXcRKlTGjklq/yBOIMfp4UFWuDcbRcO32dIJOY1VCKcwpoDE6lcHgA== 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= fm1; t=1717631485; x=1717717885; bh=kABoX+02IoACBJ1bLYrQWx+lYHkB 0Qf9GWADQVdTAzc=; b=BA2RCUj52S9g/lFyNKBh9fmw98sVvs0RHG7Y2FbCdZXd Z7G+Wu/UFqPzK+7Ge6ZbmapCkYWJ2VZErBOC2Wayq+4e2UB+I2hOtrPKL/30U7o6 MXPjFMv5RLaiEsCEYSXtBhe+iVK2BnYs86dJY4koKhl0r7tvC6aJKVfWhZYTpLyK MgeOveR2ib/dsh7ThufSroGTjnPlLYDZUS35hzKHPeM2HBbnqnYr53XPHAksc8O4 GEyC+xEb+Xfsca9xnzEO31wBu9v7V5/cvb7FriYQcBQ0I3kXbFx6+dQDIf44Kkr/ dfXdrIvPy9wxN3qNJd5wRF7tN2PpaRPTaIvYQWEDUg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeljedgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Jun 2024 19:51:22 -0400 (EDT) Date: Thu, 6 Jun 2024 08:51:10 +0900 From: Michael Paquier To: Floris Van Nee Cc: Andres Freund , Kyotaro Horiguchi , "exclusion@gmail.com" , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure Message-ID: References: <17947-b9554521ad963c9c@postgresql.org> <20230601.084245.1524588196504400333.horikyota.ntt@gmail.com> <20240505183741.5tefii3razzefvtc@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GutFD5T00eO8jbTe" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --GutFD5T00eO8jbTe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 05, 2024 at 10:24:43AM +0000, Floris Van Nee wrote: > I noticed it but wasn't sure if it was necessary here due to the exceptio= nal case here. > It raises ereport error right after and can only reach this if the entry = was created > In the call to pgstat_prep_pending_entry before it, so it seems unlikely = another > backend holds a ref to it. I might be wrong though. It does not prevent addressing the original issue, so pushed down to 15 after running concurrent tests for a few extra hours. >> Attached is an updated patch with refined comments at the top of ? >> pgstat_drop_entry(), to be applied to 15~. >=20 > Thanks for testing the patch. Updated patch looks good to me. I'll try to look at this one separately. -- Michael --GutFD5T00eO8jbTe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmZg+e4ACgkQnvQgOdby QH2FNA/+NPYD5eIZxj2n5p4TWVbTkBpaGzjUEmZD3NXspDbW0pL6ScDAAQxBKSua Wunqc8TilfKQHh1j82caJ2JYNBG7c+v75TCkdjQe7dNfn/sERYPDbOpSNVfCoWNz cNpuD8v48bpSZHxKHAhz3I5UhnK1+GD/xIvZUmxjIIQor8Tsw7KyaSg/4s5PVGII OcGgRZAF5AnF5Kpcj8Yf/LayMtrJWVUEp0FlWmphbXmrsZ042uDbSHAdy9fYStSX W4w9kiO0rG7QNZv2OczL+osRVT0NyUBldu/S+Xd/VhfObUZXCad5z902mUg+ANeq TtOr2plBdrADb0U5PR6BHSg9apCUq8CzoeWq1nlILEk+ZVVcEhr3y9Mnk9sRJPyN A4PVS71JYVgr5t9F63qIf35zxPTSAuc2yE4J/IiToPuHHobLhSt9lXaZtdk6Meb3 PqF4+0Ut/qd3yaFmNXGRufHJbsNRGwe3gF24SmCG4taoCe7sFWLizgXfCddS2fSL HgJKdhbRqjMxCi+/O65nFFlMcZCjU4KgzMZHFBAScqfVUCkIMlU5ifffevUQ+Lq+ y7//tmfxT9nOMD+lOW9tyjGDgedjtIbLJZO8gqtHZ0k8AldqzJ9GIeJrx8GXKEcd PA1qPE35TC0/W45KBR1gDhWbkWJNH13RfRKTSnovJNLQTmLvSq8= =JgxE -----END PGP SIGNATURE----- --GutFD5T00eO8jbTe--