Horton
Menu

Re: analyze-in-stages post upgrade questions

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Mircea Cadariu <cadariu.mircea@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, "Zechman, Derek S" <Derek.S.Zechman@snapon.com>, Adrian Klaver <adrian.klaver@aklaver.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-18T02:36:48Z
Lists: pgsql-hackers, pgsql-general 
On Thu, Aug 7, 2025 at 3:14 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
> I also am leaning towards treating this as v19 material.  It's a nontrivial
> behavior change, and this option is useful for major version upgrades,
> which is an area that we really don't want to surprise users too much.

+1

> Furthermore, auto-analyze doesn't process partitioned tables, either, so
> this introduces a bit of divergence.  (I'd love to see that project picked
> up again someday.  Perhaps I will take a gander...)

Sounds good!

Regards,

-- 
Fujii Masao

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. vacuumdb: Make vacuumdb --analyze-only process partitioned tables.

  2. Integrate FullTransactionIds deeper into two-phase code