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 1rMrm0-007Fpe-VG for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jan 2024 15:42:45 +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 1rMrlz-005ux1-Ra for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jan 2024 15:42:43 +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 1rMrlz-005uws-8y for pgsql-hackers@lists.postgresql.org; Mon, 08 Jan 2024 15:42:43 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMrlw-000Uu8-CV for pgsql-hackers@lists.postgresql.org; Mon, 08 Jan 2024 15:42:42 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3997A5C0FE1; Mon, 8 Jan 2024 10:42:38 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 08 Jan 2024 10:42:38 -0500 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 :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704728558; x= 1704814958; bh=j/A5lYpg9AP4kuad2BQsyJMSigcaQpuMNSnOmAsZIB8=; b=1 Ow1Reo9Tp03v/eVDv/R8mQ0LakeNpFnQkXOpzYbqMqYuHw0OLt/JCr20/H2F8yb9 m3eWbPZse38KHCjd/toVhas9cRRr5ZLa0CEmGjnK/ZhUnph3dWWIJIdD7KfE1UH9 Vdwm+DpkwARGtERHriFSBqbbNRN+A5Cchkf7aXJ/BsbmLcOywqpGuJ1KwE7JNyPe UspNnThXIljzQrplEXFSEAFCu+F9gti18XWwB1fwbsfrZarhasmFg+YcZTCtztoq tjuc6Umjjbg6IoQCi23mKGFtzZH2oxfyD66Fi41as2CLCW0udNBv3LSnc1ucxJku IkMUSWNKnbil82H/0hbMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehjedgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 Jan 2024 10:42:37 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1704728554; bh=IkF09WA8oBqnnOpjNNd1ZpgZfDBcsXHbpc/Ly7KSQ4U=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=dsi8POki1t11cHwsF5TtOmw9arweSpgBuTTLWKAMf+rmo3soKVlx9GjU5IXkvT7KZ LvwqMCEs+pcm8CjL27mebeV2He6yCeIXi0vnShZ1j9fy0nfYqA/PfXewuC0tBVcmwN 1nhbR0ERFf7agdS3I0T+Jky7YgKnRk/nTqjZeO5djCo4gIg3rNxzRzvIqXxloRjq1L 6zkZG86a4jloJeNyaPQWgFDWdBC19uHGM8FDqAirKbJvSDHKr4yLJ80A0bXJmNws8Z v+nYVNoLfteh24Zg4JB8B/JG/Q4hb6p31xzA6zygZDWlr+5bjcndpjM5VR0bvR0rjN xnfjxoy6I7Svw== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 8FCCE9D; Mon, 8 Jan 2024 16:42:34 +0100 (CET) Date: Mon, 8 Jan 2024 16:42:34 +0100 From: Alvaro Herrera To: Dilip Kumar Cc: tender wang , PostgreSQL Hackers Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock Message-ID: <202401081542.fzxp7f7jhs5w@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-Jan-08, Dilip Kumar wrote: > On Mon, Jan 8, 2024 at 4:55 PM Alvaro Herrera wrote: > > > > The more I look at TransactionGroupUpdateXidStatus, the more I think > > it's broken, and while we do have some tests, I don't have confidence > > that they cover all possible cases. > > > > Or, at least, if this code is good, then it hasn't been sufficiently > > explained. > > Any thought about a case in which you think it might be broken, I mean > any vague thought might also help where you think it might not work as > expected so that I can also think in that direction. It might be > possible that I might not be thinking of some perspective that you are > thinking and comments might be lacking from that point of view. Eh, apologies. This email was an unfinished draft that I had laying around before the holidays which I intended to discard it but somehow kept around, and just now I happened to press the wrong key combination and it ended up being sent instead. We had some further discussion, after which I no longer think that there is a problem here, so please ignore this email. I'll come back to this patch later this week. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "El que vive para el futuro es un iluso, y el que vive para el pasado, un imbécil" (Luis Adler, "Los tripulantes de la noche")