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 1rdBpX-004JZv-KV for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Feb 2024 16:21:52 +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 1rdBpW-00CVo2-1O for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Feb 2024 16:21:50 +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 1rdBok-00CT55-G1 for pgsql-hackers@lists.postgresql.org; Thu, 22 Feb 2024 16:21:03 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdBoh-000SYL-0E for pgsql-hackers@lists.postgresql.org; Thu, 22 Feb 2024 16:21:01 +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 41MGKs1o551455; Thu, 22 Feb 2024 11:20:54 -0500 From: Tom Lane To: Dean Rasheed cc: zwj , pgsql-hackers Subject: Re: bug report: some issues about pg_15_stable(8fa4a1ac61189efffb8b851ee77e1bc87360c445) In-reply-to: References: Comments: In-reply-to Dean Rasheed message dated "Wed, 21 Feb 2024 17:00:45 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <551453.1708618854.1@sss.pgh.pa.us> Date: Thu, 22 Feb 2024 11:20:54 -0500 Message-ID: <551454.1708618854@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Dean Rasheed writes: > Attached is a patch that prevents UNION ALL subquery pullup in MERGE only. I think that this is a band-aid that's just masking an error in the rowmarking logic: it's not doing the right thing for appendrels made from UNION ALL subqueries. I've not wrapped my head around exactly where it's going off the rails, but I feel like this ought to get fixed somewhere else. Please hold off pushing your patch for now. (The test case looks valuable though, thanks for working on that.) regards, tom lane