Re: track generic and custom plans in pg_stat_statements - Mailing list pgsql-hackers

From Ilia Evdokimov
Subject Re: track generic and custom plans in pg_stat_statements
Date
Msg-id 1d667f28-c739-417b-b024-7f5c1004a008@tantorlabs.com
Whole thread Raw
In response to Re: track generic and custom plans in pg_stat_statements  (Sami Imseih <samimseih@gmail.com>)
Responses Re: track generic and custom plans in pg_stat_statements
List pgsql-hackers
After the introduction of pg_overexplain extension and Robert's comment 
[0], I'm starting to have doubts about whether it's still appropriate to 
add this information to EXPLAIN itself. If there are compelling reasons 
that showing the plan type would be broadly useful to users in EXPLAIN, 
I’m happy to proceed. Otherwise, perhaps this is something better suited 
for extension.

[0]: 
https://www.postgresql.org/message-id/CA%2BTgmoZ8qXiZmmn4P9Mk1cf2mjMMLFPOjSasCjuKSiHFcm-ncw%40mail.gmail.com

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




pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Remove unnecessary static type qualifiers
Next
From: Jakub Wartak
Date:
Subject: Re: BAS_BULKREAD vs read stream