MIME-Version: 1.0
References: <PH0PR04MB8294E796D6297D4E3BE4EFB6C049A@PH0PR04MB8294.namprd04.prod.outlook.com>
 <08d943a83590308cbb9be594d80b4e19ca80e08e.camel@cybertec.at>
 <2505eef1-b6aa-4518-baff-861a2e6a507b@gmail.com> <b65126bf381d4b41f561afe691000b77ac7b8cc2.camel@cybertec.at>
 <a018a729-9b18-444f-baed-be0d6d8ecb80@gmail.com> <2c1f1834107045dfa8b32417771b56bab0cffc56.camel@cybertec.at>
 <2cce9851-327a-4b1a-ab8e-531c2f92532b@gmail.com> <CAHGQGwEvwpydO7hjnB51Q2zgS0ydv31X4HCFLNzMeqLr=poS8w@mail.gmail.com>
 <9c9cb744-b8c7-4d75-acad-595b3faba187@gmail.com> <CAHGQGwEj8PCk1OVveJ_F1sj_COrV95N-mfu_tLUn4gdcAM24kA@mail.gmail.com>
 <aJObdBmd9H5YAdW1@nathan>
In-Reply-To: <aJObdBmd9H5YAdW1@nathan>
From: Fujii Masao <masao.fujii@gmail.com>
Date: Mon, 18 Aug 2025 11:36:48 +0900
Message-ID: <CAHGQGwGhWjhKPZsorB6QG64dmaO0fVNERuWvfn98BYjVjT22EA@mail.gmail.com>
Subject: Re: analyze-in-stages post upgrade questions
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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAHGQGwGhWjhKPZsorB6QG64dmaO0fVNERuWvfn98BYjVjT22EA%40mail.gmail.com>
Precedence: bulk

On Thu, Aug 7, 2025 at 3:14=E2=80=AFAM Nathan Bossart <nathandbossart@gmail=
.com> wrote:
> I also am leaning towards treating this as v19 material.  It's a nontrivi=
al
> 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 picke=
d
> up again someday.  Perhaps I will take a gander...)

Sounds good!

Regards,

--=20
Fujii Masao