| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Nathan Bossart <nathan(at)postgresql(dot)org>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | vacuumdb --missing-stats-only and pg_upgrade from PG13 |
| Date: | 2025-04-23 14:01:33 |
| Message-ID: | aAjyvW5_fRGNr7yF@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Re: To Nathan Bossart
> > Update guidance for running vacuumdb after pg_upgrade.
> >
> > Now that pg_upgrade can carry over most optimizer statistics, we
> > should recommend using vacuumdb's new --missing-stats-only option
> > to only analyze relations that are missing statistics.
>
> I've been looking at vacuumdb --missing-stats-only because Debian's
> pg_upgradecluster is using that now.
The reason I was looking closely yesterday is because Debian's
regression tests were tripping over it, but I only figured out the
problem today:
If I create a table in a PG13-or-earlier cluster, never ANALYZE it,
and then pg_upgrade to 18 and run vacuumdb --analyze-only
--missing-stats-only, the table will not get analyzed. The only table
visited there is pg_largeobject.
Upgrades from 14..17 are fine.
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2025-04-23 14:10:56 | Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. |
| Previous Message | David E. Wheeler | 2025-04-23 13:57:46 | Re: extension_control_path and "directory" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2025-04-23 14:10:56 | Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. |
| Previous Message | David E. Wheeler | 2025-04-23 13:57:46 | Re: extension_control_path and "directory" |