Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUuzY-0006vb-IZ for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Mar 2022 18:36:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUuzX-0001Ox-DY for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Mar 2022 18:36:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUuzW-0001Oo-C8 for pgsql-hackers@lists.postgresql.org; Thu, 17 Mar 2022 18:36:55 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUuzS-0003xL-G8 for pgsql-hackers@lists.postgresql.org; Thu, 17 Mar 2022 18:36:54 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 2F041580129; Thu, 17 Mar 2022 14:36:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 17 Mar 2022 14:36:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=kaHfSninUrBHVYM6AM3oeBd9giALwcyHcALPTU9uCyQ=; b=mO7TJ9Js abxiEbfCMaAJdwY1q3LmIq3fptsyBBp0FOrlTN2awFj8RVZ1wyLP2JmaIVbbNlFJ tP44+vyH/t5XhQG6QcOuRGbYcnzRWH4YJNfBZ6kKsMW4/JKAGWcwDu/2tR/F82rB fq236ttc3ZevB4fN5ZKauvhtwxxLvVbMXSK7WDDuUQjUBIbc1ZVXHMLN6JR9JK5u msiTuym8rJB2Julw2lnSIn9ub904f2kofH1mu9fc0e2UgjB8OtsaaeIUmbyqaCAn uHExVJBY8fRHsQI5+CKZRaBqExTr5IGYuPqz6M5RBDNlM42zTGtdfxEEN98bcF9Q quNPBUEAIVJZ6g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefgedguddufecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enogfvvgigthfqnhhlhidqqdfuphgrmhgsohhtqdgkgedvvddqjeduqdgsihhsucdlfedt tddmnecujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlh hvrghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdho rhhgqeenucggtffrrghtthgvrhhnpefgheegjeffvddvfeffhfegudevtdekgfffteeive ejffeitdeugeeiveeuudfgtdenucffohhmrghinhepphhoshhtghhrrdgvshdpphhoshht ghhrvghsqhhlrdhorhhgpdgvnhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 17 Mar 2022 14:36:47 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 30D382A0A2E; Thu, 17 Mar 2022 15:36:48 -0300 (-03) Date: Thu, 17 Mar 2022 19:36:48 +0100 From: Alvaro Herrera To: Justin Pryzby , Amit Langote , Japin Li Cc: Zhihong Yu , Simon Riggs , Pg Hackers , Tomas Vondra , Daniel Westermann , Erik Rijkers , Jaime Casanova , Andres Freund Subject: Re: support for MERGE Message-ID: <202203171836.ewk25joolhwc@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202203171131.xiydwhlpde2a@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Mar-17, Alvaro Herrera wrote: > I'll see what to do about Instrumentation->nfiltered{1,2,3} that was > complained about by Andres upthread. Maybe some additional macros will > help. This turns out not to be as simple as I expected, mostly because we want to keep Instrumentation as a node-agnostic struct. Things are already a bit wonky with nfiltered/nfiltered2, and the addition of nfiltered3 makes things a lot uglier, and my impulse of using a union to separate what is used for scans/joins vs. what is used for MERGE results in an even more node-specific definition rather than the other way around. Looking at the history I came across this older thread where this was discussed https://postgr.es/m/20180409215851.idwc75ct2bzi6tea@alvherre.pgsql particularly this message from Robert, https://www.postgresql.org/message-id/CA%2BTgmoaE3R6%3DV0G6zbht2L_LE%2BTsuYuSTPJXjLW%2B9_tpMGubZQ%40mail.gmail.com I'll keep looking at this in the coming days, see if I can come up with something sensible. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ Y una voz del caos me habló y me dijo "Sonríe y sé feliz, podría ser peor". Y sonreí. Y fui feliz. Y fue peor.