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 1nrMe2-00029z-LK for pgsql-hackers@arkaria.postgresql.org; Wed, 18 May 2022 16:35:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nrMe1-0008MN-I1 for pgsql-hackers@arkaria.postgresql.org; Wed, 18 May 2022 16:35:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrMe1-0008ME-90 for pgsql-hackers@lists.postgresql.org; Wed, 18 May 2022 16:35:29 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrMdx-0006KM-As for pgsql-hackers@lists.postgresql.org; Wed, 18 May 2022 16:35:28 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 8917A3200979; Wed, 18 May 2022 12:35:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 18 May 2022 12:35:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id: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=fm1; t=1652891722; x=1652978122; bh=S 4qsfpRSP4javz9nNqN2K3R7HPmTGQsdjLtwrHT/p8Q=; b=foiIrWD27xexJNgyY V4uG6Mh9cNqHMvKTVPN1Yg1EL/IS2CS0nFoTOlXWgoE+45rYWf2z5/2491dn1wPM tqq78goOHyxK7Y+enhSGquK8jqyDc3ZF+O4G7d+HAvgqdFc8F52fsghADAdpa/m0 90VmdpKnoFQjmDq7tTPzK/1Hljwlo7rtz3mNVuiQucWraNLJx+v8obvv4qIq8RvR w/IOIhknUNm9xxBxLqHYK0kFfsyODPjhtLr14g0RPfeFf3YOFXKpfVgZJb1lE75y QATu6sc9Cvd8dFqoP97HhHO04CmL0jWCIfczhCAgOx5IOtkE6R7mXHYb6st/jLP+ 3xG/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrheelgddutddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 May 2022 12:35:21 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 0B41A2A1E42; Wed, 18 May 2022 18:36:01 +0200 (CEST) Date: Wed, 18 May 2022 18:36:01 +0200 From: Alvaro Herrera To: Justin Pryzby Cc: Peter Eisentraut , Amit Langote , Japin Li , Zhihong Yu , Simon Riggs , pgsql-hackers@lists.postgresql.org, Tomas Vondra , Daniel Westermann , Erik Rijkers , Jaime Casanova , Andres Freund Subject: Re: support for MERGE Message-ID: <202205181636.v26g2zvkeeks@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220518123005.GA9638@telsasoft.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-May-18, Justin Pryzby wrote: > On Wed, May 11, 2022 at 11:33:50AM -0500, Justin Pryzby wrote: > > > That's separate from the question about eliding zeros. > > Actually, the existing uses suggest that these *aren't* separate. > > The cases where 0 output is elided (like Heap Blocks and Buffers) uses "=" and > not ":". The cases using ":" always show all fields (Sort Method, Buckets, > Hits, Batches). I'm not sure which is preferable for MERGE, but here's one > way. I chose the other way :-) -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/