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 1sg6ZD-00FMk8-54 for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Aug 2024 17:53:19 +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 1sg6YC-0013Pu-Qm for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Aug 2024 17:52:17 +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 1sg6YC-0013Pm-HK for pgsql-hackers@lists.postgresql.org; Mon, 19 Aug 2024 17:52:17 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sg6Y9-000U29-Lr for pgsql-hackers@postgresql.org; Mon, 19 Aug 2024 17:52:16 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 47JHq7Zr1393411; Mon, 19 Aug 2024 13:52:07 -0400 From: Tom Lane To: Robert Haas cc: Amit Langote , Alvaro Herrera , Andres Freund , Daniel Gustafsson , David Rowley , PostgreSQL Hackers , Thom Brown Subject: Re: generic plans and "initial" pruning In-reply-to: References: <202406191709.jbvpf7d7hl6g@alvherre.pgsql> <1386845.1724086454@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 19 Aug 2024 13:38:28 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1393409.1724089927.1@sss.pgh.pa.us> Date: Mon, 19 Aug 2024 13:52:07 -0400 Message-ID: <1393410.1724089927@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > But that seems somewhat incidental to what this thread is about. Perhaps. But if we're running into issues related to that, it might be good to set aside the long-term goal for a bit and come up with a cleaner answer for intra-session locking. That could allow the pruning problem to be solved more cleanly in turn, and it'd be an improvement even if not. > Do you have a view on what the way forward might be? I'm fresh out of ideas at the moment, other than having a hope that divide-and-conquer (ie, solving subproblems first) might pay off. > This thread has gotten a tad depressing, honestly. All of the opinions > about what we ought to do seem to be based on the firm conviction that > X or Y or Z will not work, rather than on the confidence that A or B > or C will work. Yet I'm inclined to believe this problem is solvable. Yeah. We are working in an extremely not-green field here, which means it's a lot easier to see pre-existing reasons why X will not work than to have confidence that it will work. But hey, if this were easy then we'd have done it already. regards, tom lane