From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "Zechman, Derek S" <Derek(dot)S(dot)Zechman(at)snapon(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: analyze-in-stages post upgrade questions |
Date: | 2025-08-18 02:36:48 |
Message-ID: | CAHGQGwGhWjhKPZsorB6QG64dmaO0fVNERuWvfn98BYjVjT22EA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Thu, Aug 7, 2025 at 3:14 AM Nathan Bossart <nathandbossart(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-08-18 02:38:23 | Re: analyze-in-stages post upgrade questions |
Previous Message | Greg Sabino Mullane | 2025-08-15 16:45:54 | Re: pgbackrest check info fails without success |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-08-18 02:38:23 | Re: analyze-in-stages post upgrade questions |
Previous Message | David Rowley | 2025-08-18 02:19:06 | Re: Compilation issues for HASH_STATISTICS and HASH_DEBUG options |