| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | VASUKI M <vasukianand0119(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: Optional skipping of unchanged relations during ANALYZE? |
| Date: | 2026-01-29 21:40:28 |
| Message-ID: | CADkLM=eYG-ug_zcsr12BoD_i+bWhqnrCt8rXH4ULui42B5_tcQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I am wondering if we should take the current SQL used by vacuumdb to
> find missing stats and perform direct syscache lookups in C?
>
So....about that. The exiting missing-stats-only queries test for a
corresponding pg_statistic_ext_data row for any pg_statistic_ext row that
meets the relation filters, but at this very moment we can restore all
types of extended stats _except_ expressions. That functionality could make
it into 19, but if it doesn't we're going to have to adjust vacuumdb to
probe pg_statistic_ext.stxkeys for expression indexes and look for matching
stxdexprs elements. I agree that those matches are better done with
syscache lookups, but the SQL that we're treating as a spec might be a
moving target in the near future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2026-01-29 21:48:39 | Re: Pasword expiration warning |
| Previous Message | Peter Smith | 2026-01-29 21:36:53 | Re: Skipping schema changes in publication |