Horton

Re: Proposal - Allow extensions to set a Plan Identifier

Sami Imseih <samimseih@gmail.com>

View thread
From: Sami Imseih <samimseih@gmail.com>
To: Lukas Fittl <lukas@fittl.com>
Cc: Michael Paquier <michael@paquier.xyz>, Andrei Lepikhov <lepihov@gmail.com>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-24T19:36:05Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow plugins to set a 64-bit plan identifier in PlannedStmt

> 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