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

From Ilia Evdokimov
Subject Re: Proposal - Allow extensions to set a Plan Identifier
Date
Msg-id 4f32c878-34e2-4f4a-8575-bf343ba6e037@tantorlabs.com
Whole thread Raw
In response to Re: Proposal - Allow extensions to set a Plan Identifier  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Proposal - Allow extensions to set a Plan Identifier
List pgsql-hackers
Hi,

Thank you for the patches. They're very important for many extensions.

I've debugged them using simple extensions pg_stat_statements and 
auto_explain, specifically checking cases involving PlannedStmt 
and pg_stat_get_activity - , and haven't encountered any issues so far.

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;

--
Best regards,
Ilia Evdokimov,
Tantor Labs LLC.




pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Proposal: Adding compression of temporary files
Next
From: Amit Kapila
Date:
Subject: Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.