Horton

Re: vacuumdb changes for stats import/export

Frédéric Yhuel <frederic.yhuel@dalibo.com>

View thread View on postgr.es
From: Frédéric Yhuel <frederic.yhuel@dalibo.com>
To: Nathan Bossart <nathandbossart@gmail.com>, Corey Huinker <corey.huinker@gmail.com>
Cc: John Naylor <johncnaylorls@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bruce Momjian <bruce@momjian.us>, Jeff Davis <pgsql@j-davis.com>, jian he <jian.universality@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, Stephen Frost <sfrost@snowman.net>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, alvherre@alvh.no-ip.org
Date: 2025-07-23T12:45:10Z
Lists: pgsql-hackers 

On 3/18/25 22:37, Nathan Bossart wrote:
> Committed with the following small changes:

Hi, I don't really understand this sentence in 
doc/src/sgml/ref/vacuumdb.sgml:

 > This option prevents vacuumdb from deleting existing statistics so 
that the query optimizer's choices do not become transiently worse.

I thought that the point was to avoid unnecessary post-upgrade analyzes?

Commits

  1. doc: Adjust documentation for vacuumdb --missing-stats-only.

  2. Update guidance for running vacuumdb after pg_upgrade.

  3. vacuumdb: Add option for analyzing only relations missing stats.

  4. vacuumdb: Teach vacuum_one_database() to reuse query results.