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 1sIzIV-001isS-57 for pgsql-bugs@arkaria.postgresql.org; Sun, 16 Jun 2024 23:28:31 +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 1sIzIS-00AxSh-FC for pgsql-bugs@arkaria.postgresql.org; Sun, 16 Jun 2024 23:28:29 +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 1sIzIS-00AxSZ-6r for pgsql-bugs@lists.postgresql.org; Sun, 16 Jun 2024 23:28:29 +0000 Received: from fout1-smtp.messagingengine.com ([103.168.172.144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sIzIQ-00228p-JP for pgsql-bugs@lists.postgresql.org; Sun, 16 Jun 2024 23:28:28 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 7E991138011C; Sun, 16 Jun 2024 19:28:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 16 Jun 2024 19:28: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=1718580505; x=1718666905; bh=c4V/U3PyqK 26uFFZSjllKfa5URsWEZKDfQACsqZWki0=; b=G0LFGqonpTQXtSSUeCCLlGjoZ6 deoCVmzuiM67S28XvfgHVCu2vpbgxzIF1pn/tqRU0vVI7uyaPcQegdxiHPcRmt59 nnj7vrdGkS5KIjxS2aIQcRhIkHGrCE4X33d4n0QuL20JlGq46TfOlbbBFqj5QOVa Bli480YRGsz+gUDhJnocsfHUvbsJQdhXQ6uf3h1c5DtuNmy2Wdx06ukIRJKqZPwk qYY+SorwjuwC6vuvvEQokiV++4O189qKOWZ/I5/F2zQHv9LUNIpzm8o+fgsuHDAl mdrTms8yzwtPf3U1Fxj2bT8MjK8PmZFzryDMyrbLJdhZSDU514rUWstS7bFg== 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=1718580505; x=1718666905; bh=c4V/U3PyqK26uFFZSjllKfa5URsW EZKDfQACsqZWki0=; b=X/dpbUsNCavGj8X9FFD5ilhjI1JhBlreKo66KwhAaAx6 4u7w0l9cMqTtEUMZrxW4+JDL6IqifvpmguSFRmvVoHd5Mszx0na7hYS4qCvwu1FE zwHA2SWPp03BTBPrhYssAWpc61QDGmEdTY1sMaOSoEhL1p+ZLl4T24nU67XsN7SJ HZ/bvXE/eMOo6VCSmj0uOVRu7AmeTLKHnClQib9/37mQbna6xcOo8xUPLwmDwXAx cmx7D7ZB5T9NfLsRgr2/BSR827E9gKYy0OnWasgOZYe8EUsi7wqycC5hX308zNyy 34oPmLkqZA+dr3ye8gzBohQPi1t8+1AbawT+vayk8g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedvgedgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlfeehmdenucfjughrpeffhf fvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghq uhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvg hrnhepgeffjeevgfevuddvjedtvddtieejheduueelvddufedtgfefjedvkeevkeeivddv necuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghr rdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 16 Jun 2024 19:28:23 -0400 (EDT) Date: Mon, 17 Jun 2024 08:28:10 +0900 From: Michael Paquier To: Kyotaro Horiguchi Cc: florisvannee@optiver.com, andres@anarazel.de, bertranddrouvot.pg@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org Subject: Re: error "can only drop stats once" brings down database Message-ID: References: <2cb577e176774caca28c724898768a38@Optiver.com> <20240611.164457.1388765109177375375.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8xjrggM8TCbVD1yd" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --8xjrggM8TCbVD1yd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 14, 2024 at 09:37:35AM +0900, Michael Paquier wrote: > I am wondering if we should tackle this problem by adding a notion of > "age" in the stats entries for what's stored in the central dshash and > in the hold copies in the backends, so as we dump the "age" of an > existing stats entry if we find out that it gets reused in a create > path. That requires some design and would not be backpatchable, but > it does not seem that invasive at quick glance (I had my eyes on this > code the full week). Other thoughts are welcome. This still sounds like a good idea after sleeping on it over the weekend. Please note that I am moving on with the problem on this thread where this has been reported, and that is the point of origin: https://www.postgresql.org/message-id/ZmvVudpT8z6hbY9t@paquier.xyz Let's continue the discussion there. -- Michael --8xjrggM8TCbVD1yd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmZvdQoACgkQnvQgOdby QH0TIRAApzmt5aqziV6s9RYrA89cpsUVFv8KuUNN3dfiES+3rZFN85CtlOITmwt7 L4u5/1IoymNQZRIerd5XUqgNu484pwUC0B5cgNeXl5op2966yoe6BWNeMQvKoXtW k65Zgmc+o7Nxjw8RdysSCp2ZDiC8QNnZPtaUGohLvtSsaYMmehVl7VMXTJ2KjK58 8XFvEYMxTWA4WLOpxyvV1AWm+KsppoeVC1IJxRY8KPdLEaUbgMzuwNoWUTPtcAlP cX44SI13YNje22AyGrpLRnuYNEw7RRAvN5trQH6m3TiEa7oCuQ9Rm1YgEyySgXjs fN3CPG8wXzIb6u0PExskgceMHGE8V49FHzv1IZx0b1/G4fb39gPoQSo3ZCli8T03 NptX4l+DpzDsictZzAErxcH72U0qGbg53ow4azbxDXUM6hRiDlfNvCqafIhoTWP/ 2fymfrAx+PvT3vDo1jX6YR/2ADbyLCFtx4iOoqnqe8HBrPn/O0Zc5+kaIwDs/FMa vm6kgKHNbPBMTv3LgPjIfNzoOUUi24b8eUKPYB1zjoIYaIDBnTMSmprh1H64JrCW JI7LxXacYRjKbdsvViKL6N3hwvbK579+K7lik0/jgd6gzx4GwRbKMdXDaLXcv2nx C9V7V/Mj9/yYMnxLZsQ5Vo5lN/miOgE1kfiDVbo18E5YWm+FJqQ= =liOL -----END PGP SIGNATURE----- --8xjrggM8TCbVD1yd--