Re: Proposal - Allow extensions to set a Plan Identifier
Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>
From: Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>
To: Sami Imseih <samimseih@gmail.com>, Michael Paquier <michael@paquier.xyz>,
Andrei Lepikhov <lepihov@gmail.com>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>, Lukas Fittl <lukas@fittl.com>
Date: 2025-03-18T12:09:19Z
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 →
-
Allow plugins to set a 64-bit plan identifier in PlannedStmt
- 2a0cd38da5cc 18.0 landed
On 18.03.2025 14:46, Ilia Evdokimov wrote: > > However, I have a question: what value should planid have when we > execute the standard planner without using a planner_hook? For > example, if pg_stat_statementsis disabled, would planid default to > zero? If zero is the expected default, should we explicitly write this > behavior? > > result->planid = 0; > Sorry for spam. I found the answer this question in thread [0]. [0]: https://www.postgresql.org/message-id/flat/CAP53Pkyow59ajFMHGpmb1BK9WHDypaWtUsS_5DoYUEfsa_Hktg%40mail.gmail.com -- Best regards, Ilia Evdokimov, Tantor Labs LLC.