| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Lukas Fittl <lukas(at)fittl(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Marko M <marko(at)pganalyze(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Optionally record Plan IDs to track plan changes for a query |
| Date: | 2025-02-13 02:50:08 |
| Message-ID: | CAA5RZ0vkNBGmz_ffiKN8vqD9S2rWH=dLXOM9d3uqN+qhefHBxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anton A. Melnikov | 2025-02-13 02:58:07 | Re: Change GUC hashtable to use simplehash? |
| Previous Message | Masahiko Sawada | 2025-02-13 01:58:12 | Re: Skip collecting decoded changes of already-aborted transactions |