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 1r7cFl-005zLc-HX for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Nov 2023 14:06:25 +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 1r7cFj-00Dt9P-Le for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Nov 2023 14:06:23 +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 1r7cFi-00Dt9C-41 for pgsql-hackers@lists.postgresql.org; Mon, 27 Nov 2023 14:06:23 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r7cFe-007bsY-VN for pgsql-hackers@postgresql.org; Mon, 27 Nov 2023 14:06:20 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 534D55C011A; Mon, 27 Nov 2023 09:06:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 27 Nov 2023 09:06:17 -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:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1701093977; x= 1701180377; bh=yL9AfhYGJLYZ9I/f9DUlYbrmKOGtQZTaoiJXXPhEczY=; b=I v2x7nkzVfVnH/Eyi62SjKhZxkThuNKMKrwPbXPuTWPBrB5VfU/JFWuKrs+BjFC6D keO5X0Icntogqn/dHgg2jRzxrQfTl3h+v6BPskGx7kq8GOjCNqUV8n6+IsQX+BT3 WtzY6JS/CKEY7qVufv9VS8Tsg8uhqymtRuz6gQyzcLG9vQ3NcA8f+U3Xk8SGi+7H jYRnqzVHykZzNgY3NJcl7I7C4xxkScb3L82+WmYlWhb5J1pPKEgr5X2V0o6eb4DV BbL7rMPFcb9FE1+DvP3LmHPfz5ye4tbdtOm5P8TaAJFC/gVsQDqxyFJnBRZam/wF tKi7eUD3dBoPlc1OEIVMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeiuddgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 27 Nov 2023 09:06:16 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1701093972; bh=cn0jhUXex8u+ZkPDQD0ARYHwCCQc7jNbra2483bZW98=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=W4dsxgeNIVNEhELqfuUZQUr+1wgO8/xQFYFK5Q8/weTgUbl6t7CMYNyFwaCqBhkLI /w+FCY+d0qTs+HO7D3ZPoHA5Ut1+St427i8joZPbk2UjQM72NHv3W/KE6RWxkJFb58 EAdQnJ3pxetQSAke6aQJH50OjviZy9tzTTpr8fNMEW3ySbYJoQ8HOYUkX2eRQbv03O n8wKG8Q8BF0Rp9+B2JjPo2k4eV2CAMUHSWJ30PPM4eViNjSG9zGopDiJAgb7XnuLBp KXZX6nMAgpVFVHc9a/yfeqNcQ+U5ulspWIPobMTe0Cgi5xQGcrZlW9fcSxgGMSTtJM tZGxJsDdciyzA== Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id D4930DB; Mon, 27 Nov 2023 15:06:12 +0100 (CET) Date: Mon, 27 Nov 2023 15:06:12 +0100 From: Alvaro Herrera To: Andrew Dunstan Cc: Amit Langote , Andres Freund , jian he , Erik Rijkers , PostgreSQL-development Subject: Re: remaining sql/json patches Message-ID: <202311271406.budphctjy3p3@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 2023-Nov-27, Andrew Dunstan wrote: > Interesting. But inferring a speed effect from such changes is difficult. I > don't have a good idea about measuring parser speed, but a tool to do that > would be useful. Amit has made a start on such measurements, but it's only a > start. I'd prefer to have evidence rather than speculation. At this point one thing that IMO we cannot afford to do, is stop feature progress work on the name of parser speed. I mean, parser speed is important, and we need to be mindful that what we add is reasonable. But at some point we'll probably have to fix that by parsing differently (a top-down parser, perhaps? Split the parser in smaller pieces that each deal with subsets of the whole thing?) Peter told me earlier today that he noticed that the parser changes he proposed made the parser source code smaller, they result in larger parser tables (in terms of the number of states, I think he said). But source code maintainability is also very important, so my suggestion would be that those changes be absorbed into Amit's commits nonetheless. The amount of effort spent on the parsing aspect on this thread seems in line with what we should always be doing: keep an eye on it, but not disregard the work just because the parser tables have grown. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "La persona que no quería pecar / estaba obligada a sentarse en duras y empinadas sillas / desprovistas, por cierto de blandos atenuantes" (Patricio Vogel)