On Thu, May 13, 2021 at 09:59:43AM +0900, Kyotaro Horiguchi wrote: > > The query_id of its own is provided because pg_stat_statements did not > expose query_id. And it has been preserved only for the case the > plugin is used without pg_stat_statements activated. Now that the > in-core query_id is available, the last reason for the special > provider has gone.
Ah I see, indeed that makes sense. However I'm assuming that pg_store_plans also requires *a* queryid, not specifically what used to be pg_stat_statements' one right, so it could also fallback on an alternative implementation if users configured one? Even if that's not the case, the core query_id can still be calculated if needed as the function is now exported.
