Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
От | Sami Imseih |
---|---|
Тема | Re: [PATCH] Optionally record Plan IDs to track plan changes for a query |
Дата | |
Msg-id | CAA5RZ0vkNBGmz_ffiKN8vqD9S2rWH=dLXOM9d3uqN+qhefHBxw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Optionally record Plan IDs to track plan changes for a query (Greg Sabino Mullane <htamfids@gmail.com>) |
Ответы |
Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
|
Список | 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
В списке pgsql-hackers по дате отправления: