> The idea of introducing explicit options such as ANALYZE (MISSING_STATS)
> and ANALYZE (MODIFIED_STATS) feels like a much cleaner direction.
> In particular, starting with MISSING_STATS as a SQL-level equivalent of
> vacuumdb --missing-stats-only seems like a well-scoped and low-risk
> first step.
> I’m happy to pivot in this direction and focus first on a clear,
> well-defined MISSING_STATS option for ANALYZE, and then revisit
> MODIFIED_STATS (possibly reusing autoanalyze-style thresholds) as a
> follow-up, once there is agreement on the semantics.
I agree with this.
Thanks!
Sami Imseih
Amazon Web Services (AWS)
