Re: Proposal - Allow extensions to set a Plan Identifier - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Proposal - Allow extensions to set a Plan Identifier
Date
Msg-id CAA5RZ0udib3f1_chVjewBrp9KLygc7ftmFyTxcHu9tzSXd9Ecg@mail.gmail.com
Whole thread Raw
In response to Re: Proposal - Allow extensions to set a Plan Identifier  (Lukas Fittl <lukas@fittl.com>)
Responses Re: Proposal - Allow extensions to set a Plan Identifier
List pgsql-hackers
> Ideally we can also land the jumble funcs work in the other thread to allow extensions to re-use the
> in-core logic for jumbling expressions found in plan node trees.

IIUC, there should be a refactor I am working on at this moment to make that
possible [0]

>> > FWIW, Lukas did start a Wiki [0] to open the discussion for what parts
>> > of the plan should be used to compute a plan_id, and maybe we can
>> > in the future compite a plan_id in core by default.
>>
>> Let's see where this leads..  I suspect that this is going to take
>> some time, assuming that we're ever able to settle on a clear
>> definition.  Perhaps we will, or perhaps we will not.
>
>
> I think there is a good chance we'll land on a reasonable planid calculation for core

I agree

> I'll be at PGConf.dev this year, would be great to do an unconference session to discuss this further.

That will be a good idea!

[0] https://www.postgresql.org/message-id/Z9khOo14yzZHCnmn%40paquier.xyz



pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset
Next
From: Nathan Bossart
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset