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 1tiPJ4-00Fdf2-BZ for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Feb 2025 02:50:26 +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 1tiPJ1-000o5e-Cu for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Feb 2025 02:50:24 +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 1tiPJ1-000o5V-16 for pgsql-hackers@lists.postgresql.org; Thu, 13 Feb 2025 02:50:23 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tiPIz-000VMP-30 for pgsql-hackers@lists.postgresql.org; Thu, 13 Feb 2025 02:50:22 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-3072f8dc069so4296821fa.3 for ; Wed, 12 Feb 2025 18:50:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739415020; x=1740019820; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IkcTtp7cnMGycYXUhPJuJ0anGctPjjQUMBkjCAq56pY=; b=Qb8wna1H2Bk1FJoaT+rm0KP0/8GyRo76a44hAZQ8DzDdZ2YLMnkpI9TrJv9icw03nS zg0G94BvURp89wu9AESAQ5G3LkjNCE+Z9m6bLVzUjlfn3+iQBK22jpjUSvTsKx59nK/I UzqZ/sdLgCw0+6TZ0MWDMOvNmGoruHr7adV9zTZK899TB1KXu2gDQpj3r4zmDabH2T8a YlGMPLmSsGq5064QC9Sgryz++5x+13VwK07kL5n21QqEk5NKI8ElPgEZs7qCf8Rg0sXa y79a+He5tNPgwkDEaCaq8UbYQRLR7xt1HeR1tIuiKVGTECyYbZ6LEmCVujiyQLgGkCkD Ba4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739415020; x=1740019820; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IkcTtp7cnMGycYXUhPJuJ0anGctPjjQUMBkjCAq56pY=; b=JMbh7tBgvZw0UiAxVWdq4nkorwGogCPNF4Zsxww95onbjsf3ZenJIEYc7w7BnS8ozz GcTtPXBZ00lXtGysAiH16ZIbxO7S0eH/mAmsVC9bAy11MMRJsAJB8pVrpbk730i6PTlj 58nCu9euVTYOzpXCwr805/BodTDaLOgoZCcLwZKCWFBAcRsmHwYRi71bYgY8JP1/Odb4 koKCH96TqB2X+03JmizcvB+LXcn4ZRrxtdamheTTjQPHoF02jX4MpTYd750IITqg74Jk t6G5TZrx5DrR4z0PhDAATK6mI4y1mkQRV3KX8oJTJPnNIXP62MiZp4CUTGa4jT6zgQ70 oarw== X-Forwarded-Encrypted: i=1; AJvYcCULfVgjRF8K7LBgs45tlQvoxZj8qvVVST6A+glFg2JnOQAUM/WJe4Q0MSsY4gRRxYH7jKVAw+ACBSJuTCam@lists.postgresql.org X-Gm-Message-State: AOJu0Yyq3kF37cfq5iz+4OFL6TOazmL61LAnlMG5AunceUcWXng0G814 i7Sf6lareU18OH9pMPalVyFz2ViJcyUO4iH9qNloAIIYTz05xGa4Ko8CjVnHc6fTfXJzeJJUFEK HDzEO+WaD37JjBoAoH5+SQdd//Bs= X-Gm-Gg: ASbGncu5fuMsOP1Ql2cx3vVozHTGDXO175KnFe3gLq6jecIXHnFxgMQBVbBKmD7J3Eb BWYDA/uYq8pGqy4gz4AG2/Wc+gtkF5Ppo7NuMiYIUIPokCX1veiSjCIj5HkHIsiYmsAcyV1g= X-Google-Smtp-Source: AGHT+IFGdNA6u2slmDnysj3o0tJzbjMB04X3zV5yWxQ1c0086GYejzmmt8ahiRyKU2w7N2JqCzGpp9ZvLJdpTP39SJw= X-Received: by 2002:a05:651c:1a0c:b0:309:2ed:72df with SMTP id 38308e7fff4ca-309036dbf68mr17946761fa.24.1739415020032; Wed, 12 Feb 2025 18:50:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Sami Imseih Date: Wed, 12 Feb 2025 20:50:08 -0600 X-Gm-Features: AWEUYZlHaQPbE4fFkmes1jIwprofBOjzk07niYdlQHTxvYlPC2NkAR2atvBB11s Message-ID: Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a query To: Greg Sabino Mullane Cc: Michael Paquier , Lukas Fittl , PostgreSQL Hackers , Marko M , Alvaro Herrera , Julien Rouhaud Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk >> On Mon, Feb 10, 2025 at 02:02:10PM -0600, Sami Imseih wrote: >> > I am OK with moving away from "jumble" in-lieu of something else, but my thoughts are we should actually call this process "fingerprint" > > > I agree fingerprint is the right final word. But "jumble" conveys the *process* better than "fingerprinting". > I view it as jumbling produces an object that can be fingerprinted. hmm, "jumble" describes something that is scrambled or not in order, such as the 64-bit hash produced. It sounds like the final product. Fingerprinting on the other hand [1] sounds more of the process to add all the pieces that will eventually be hashed ( or jumbled ). hash and jumble are synonyms according to Merriam-Webster [2] -- Sami [1] https://en.wikipedia.org/wiki/Fingerprint_(computing) [2] https://www.merriam-webster.com/thesaurus/hash