Re: track generic and custom plans in pg_stat_statements

> So, analysing
> pg_s_s data, it would be beneficial to determine if a generic plan is
> effective or not.

Yes, this is the point of adding these statistics to pg_s_s.

> In practice, with this knowledge, we can access the CachedPlanSource of
> the corresponding PREPARED statement via an extension and override the
> decision made in 'auto' mode. Unfortunately, we cannot obtain a pointer
> to plan cache entries for plans prepared by the extended protocol, but
> this may be possible in the future.
>
> So, I meant that the source of the plan is one important characteristic,
> and the type (custom or generic) is another, independent characteristic

The concepts of custom and generic plan types are associated with plan caches,
so they cannot have a different source. right?

--
Sami