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 1tfT1x-002bw6-C4 for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Feb 2025 00:12:38 +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 1tfT1w-00A1Yp-9F for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Feb 2025 00:12:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfT1v-00A1Yg-FQ for pgsql-hackers@lists.postgresql.org; Wed, 05 Feb 2025 00:12:35 +0000 Received: from fhigh-b6-smtp.messagingengine.com ([202.12.124.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tfT1s-003KLc-0u for pgsql-hackers@lists.postgresql.org; Wed, 05 Feb 2025 00:12:35 +0000 Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.stl.internal (Postfix) with ESMTP id 643902540043; Tue, 4 Feb 2025 19:12:30 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-04.internal (MEProxy); Tue, 04 Feb 2025 19:12:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1738714350; x=1738800750; bh=a8fW1+Ogkl OFRwsj3snYqG4L/gBX6gyn4akMd8LRIHI=; b=dLjFPofTK+eXX0IknCU7IrqS3g 1EwI3BTW22zYayk/apZoPsTC2CSIk2FuzfVggyPkST+LEMhZ2FnzSspf3Rgn9lyn TskLP6D8Os6Hnhj0rsm62WnspNEl67CparCQc6g/0Zitzf6TZXqM+IQugqBJpFNd kItub6uE3//VBWgbfpCrJzxy0Mzsbau05mzFvRWLVmZn+ci58aFfcB+8OO1/Fevr xzhlX55cgHjlGp2VfujdsevkO6DBbZqT5kglFwsuoOR9OiGB8vU66e/GxDUZaYhN pBS0ydkEO8z9mMs66LPnkBuEmh8CDrmtk3UAFpeWAe1vd1Wzn8zYJuC9xqbg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1738714350; x=1738800750; bh=a8fW1+OgklOFRwsj3snYqG4L/gBX6gyn4ak Md8LRIHI=; b=bCWOQgoLRbtOHHV0RgwsdJrt4B4XZ3BA6aGnxQ18QBT6v0li2Fi TnKCYXLXgvGR5JpWbLD0Cu9f8AZZq1SIc2+ciz1RK88G7BDksb5hkURnGRFB3qTa gg6ZPvMa4wdwISpetamWhUEdxqJA5vVkA0BRWzNF7CgWhbSXHGIKxO7hbbzm4Eue Dz43Qa0z/S2qz4t8Op9yz9qq0HGUGrotG5Sn/NpC59csq1zXepi/WCwmZKksNDcf QVpJv6FeuwIeVSY15jmBGnpBoHo/2TzfRCYHjprVEshq8ZXcWmo4/uFZNoE6N+nh 5itwiH29RBp1u1lXtG0AoC4ExRHcABsziyA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvudelhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffk fhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrh cuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeet leeifedufffhhfdtteelgeeggeffhfekueevteeigfduudevudetgfegiedvjeenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghl sehprghquhhivghrrdighiiipdhnsggprhgtphhtthhopeegpdhmohguvgepshhmthhpoh huthdprhgtphhtthhopehsrghmihhmshgvihhhsehgmhgrihhlrdgtohhmpdhrtghpthht oheplhhukhgrshesfhhithhtlhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhhrggtkh gvrhhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopehmrghr khhosehpghgrnhgrlhihiigvrdgtohhm X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 4 Feb 2025 19:12:28 -0500 (EST) Date: Wed, 5 Feb 2025 09:12:14 +0900 From: Michael Paquier To: Sami Imseih Cc: Lukas Fittl , PostgreSQL Hackers , Marko M Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a query Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6Xwpn9qNqLlCl205" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --6Xwpn9qNqLlCl205 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 04, 2025 at 05:14:48PM -0600, Sami Imseih wrote: > Here are my high-level thoughts on this: > 1. rename queryjumblefuncs.c to jumblefuncs.c If these APIs are used for somethings else than Query structure, yes, the renaming makes sense. > 2. move the query jumbling related code to parser/analyze.c, > since query jumbling occurs there during parsing. Not sure about this one. It depends on how much is changed. As long as everything related to the nodes stays in src/backend/nodes/, perhaps that's OK. > 3. Rewrite the comments in the new jumblefuncs.c to > make it clear the intention of this infrastructure; that > it is used to jumble nodes for query or plan trees. Seems to me that this could be done before 2, as well. > I can work on this if you agree. I'd welcome an extra patch to rework a bit the format of the comments for the Plan nodes, to ease the addition of pg_node_attr(), making any proposed patches more readable. -- Michael --6Xwpn9qNqLlCl205 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmeirN4ACgkQnvQgOdby QH2chg/+O/y5ziUEa6Az4EriZpcR8eagNOp25mO6LP7aYQOZ3R3YyHgJglg/BXWV WdsO1W7NUziAvM1S/AMD6FlfdpLVDPC1gD+VULJ448B+4jrtDToucCJcZvJZG2V9 r7J5LZvViVLt+c8tk9Ex/gVxgSqcsZfBSns4e3eCWHMmHS1cUD1gPoedFYRQVvGl 9siYFHHC7zaTGetqD2oHR9rHNxu3ShwtggGgkH5IHZuD6FymLQ+jlP6sJgav12sl LUW+r9xZGQyMK7qf8cqthoJGrb83nTdRHu9sGyj3LMZ3YSZc8Ck4dkKFsQkpGJSv NqRvW5OZHyp8RwS+cBO60N9dDZGTxVWk6+nsqsAId/ToRwt4880mRz9pPgSR+Amw oq1rbV/GScUEEFSeaIz0LJhfklxv0sNHiEpoB8qgvOg+PPZvkNudPjFMJg9NL0m6 ySbYBOkyVeozSIOlIvt+xIIPYWaT0QlFgiuEmOw/YM2r28hh0wLfVPqOo5UqJKPi VsXTMHoDN0p/L7KBFZ/P+QChTQNauwdQKwOAdzAGvmtE/ghKaZS5crH9cNGaAEyZ dlhapstY5uqxXI0PrPqHWt684XD0Q90526zVpqJH4JCTwedYSgqitqrHdv56zaTJ gpz8WHopMlwvbU7LWLJ9Oxp9zE3tEE9MgcdjWL4oc0pTEalG1wU= =hR+i -----END PGP SIGNATURE----- --6Xwpn9qNqLlCl205--