Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Optionally record Plan IDs to track plan changes for a query - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Date
Msg-id CAKAnmmL3OhEg1p6EWR6tbAb1OcarnfRGARcmUut4Mp68VCNWjg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Optionally record Plan IDs to track plan changes for a query  (Lukas Fittl <lukas@fittl.com>)
Responses Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
List pgsql-hackers
Tree view
On Tue, Feb 11, 2025 at 7:08 PM Michael Paquier <michael@paquier.xyz> wrote:
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.

> For node attributes we can specify "fingerprint_ignore" or "no_fingerprint". What do you think?

Still should be jumble_ignore.

Cheers,
Greg


--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Allow io_combine_limit up to 1MB
Next
From: Sami Imseih
Date:
Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a query