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 1pIQZM-0005wT-2S for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Jan 2023 08:46:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIQZK-0002HR-VY for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Jan 2023 08:46:46 +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 1pIQZK-0002DP-M8 for pgsql-hackers@lists.postgresql.org; Thu, 19 Jan 2023 08:46:46 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIQZI-0006Ki-IN for pgsql-hackers@lists.postgresql.org; Thu, 19 Jan 2023 08:46:46 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 1DD0D32008FF; Thu, 19 Jan 2023 03:46:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 19 Jan 2023 03:46:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1674118000; x=1674204400; bh=7wWZpyIF+o 2wtl5QCCQucPyTosieTiAidnPt9pSVz8k=; b=LwCLIka2aEtQn/TMtPa3j2JHrh KME3Y/1BvMIvPqR7SuT0CX5OX1XVYCb0G059eC9HiXMlsPaN46BZIQsYCdW/8ObV fPx6pvg0KQKsm66lqVPowFNqcD+jNKMG3THWYgAq3XF5dffqsFno/CmPisGPeJzA b3soOaU3MS0R12kHPUDwCuZHeqLGnltmxtUdc+/AoeEaiPJQ5k1lV5nFjP3UrxXT xXcZRhYJeESqg0n+CjIuFTjcdw6w6z5OORZPFOYVFN0Y51BZ4cni6VuxNQ1Wk3Uj NKC9D0v1nH5EWGoJfMsyId23erkCP8QAhhdcyJO9Uncd9xbKEV5NO6zfM/Aw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1674118000; x=1674204400; bh=7wWZpyIF+o2wtl5QCCQucPyTosie TiAidnPt9pSVz8k=; b=b/PcVYjJ/rkd26LyFleIY4rGd1lEm5Y8hgSeOvXMGdgY 1k0/tgihxVoATzN8ovS6HF+UtOXgbYYQd96ok2DQA4kJkw5xDYEufXtpXfpYbFUx l9uqr1Gmr7Rld6LsHvo4REWoDrkJzZ2IKn0btm84h7icPaq+q5jNT940S0Y3sevc aTDvPIKG/RAx4qsMP9ZBf+E5PBvu369e6gW1/7bz3sqW+TVNebT4mM/sqH39UZxJ nh0honBm6+u9fJTWnNX/7U6iVgTXewYpr7Q6tBdrajWh7ZfPPR9iXC+UU+5wgwCu tkqNfhK9JAXE0A8fTYdENL0SD7I1g8+fJ0a//YVRUw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddtledguddvgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enfghrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreer tddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlse hprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteel geeggeffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdig hiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Jan 2023 03:46:39 -0500 (EST) Date: Thu, 19 Jan 2023 17:46:37 +0900 From: Michael Paquier To: Peter Eisentraut Cc: Postgres hackers , "Drouvot, Bertrand" Subject: Re: Generating code for query jumbling through gen_node_support.pl Message-ID: References: <34491a4e-2664-6ea7-662c-b13d18d2a92d@enterprisedb.com> <50b571dc-e0c0-22be-9803-4a3480d2e792@enterprisedb.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="843NbMPVj6YtKBVm" Content-Disposition: inline In-Reply-To: <50b571dc-e0c0-22be-9803-4a3480d2e792@enterprisedb.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --843NbMPVj6YtKBVm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 19, 2023 at 09:42:03AM +0100, Peter Eisentraut wrote: > I see that in the 0003 patch, most location fields now have an explicit > markup with query_jumble_ignore. I thought we had previously resolved to > consider location fields to be automatically ignored unless explicitly > included (like for the Const node). This appears to invert that? Am I > missing something? My misunderstanding then, I thought that you were OK with what was part of v1, where all these fields was marked as "ignore". But you actually prefer v2, with the second field "location" on top of "ignore". I can update 0003 to refresh that. Would you be OK if I apply 0001 (with the comments of the locations still reshaped to ease future property additions) and 0002? -- Michael --843NbMPVj6YtKBVm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmPJA2wACgkQnvQgOdby QH1S9RAAplK5bOQ+Sg+3p/FOxW7DjfTSXMKVukf01i9QCw97EgnIUUDxJKjrNNIC 4rqBvoMLiflFbOohewhxYUo8D8o14HJcyhJDqW/v5QoioYw2u0SF+ornEyNqO/Gs ibT99eefKAVV6YZpFWiSggLHMmEcOnIVd3QPa4pNjHBcC1SM8/c1m/N1wGaxRS7x Ca2uO8I6M7NeZluXhw9YIkHG817jDHK8vRqFxTRHuvLzFzUlKdBusEE2kvXYJPYT 1EAyxxYn/uLvhyyBOnBWdHwm9PT/QmKrZAkIVpphi+D6YhCLQaDA8FnA98GKvIpz PwNvoMgkl+IFv0+g+A3quAJXUsGakmXEGXxWNR5mOwuu9HKRvyV5h5w0tETgC34S e7pWrgwQpx+gqiiRzQNCPVVeYRp9GchwmKH3Pchf1JMLclNEYbwS3ro0wFUZ81w5 NOh+Cl0HHquhVCHydaY+qCadwHt5TtV2+tbi4sZg1bEsU6J4SloAJHg+OvwHRsH5 R5etV52WIx3Sm83oDGN0758HEerYDiY1DwNuiIxG2tfO1+AdVr2TKrdJ8TZRzLKn 7wJrQSUdHGX6WMLAtYBpgEkXurSpW4y0z9W0+IBPZwu3/HHuDzMsbF8zTdzr4erv fT2u9xUxuOAABm4Li8C66R0Z/Y6a/I3HS36Fv0nF100vBphilCc= =A3ZZ -----END PGP SIGNATURE----- --843NbMPVj6YtKBVm--