Thanks for the patch!
> This is conceptually similar to vacuumdb --missing-stats-only, but exposed
> at the SQL ANALYZE level for interactive and scripted use.
What is being proposed in v3 is not similar in behavior.
I am wondering if we should take the current SQL used by vacuumdb to
find missing stats and perform direct syscache lookups in C?
The benefit there is we can also change vacuumdb to use the ANALYZE
(MISSING_STATS) option
directly rather than deriving the SQL, and the MISSING_STATS behavior
will be the same
if we do this type of analyze from vacuumdb or manually via ANALYZE command.
Attached is the query used by vacuumdb on HEAD.
What do you think?
--
Sami Imseih
Amazon Web Services (AWS)
