From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(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-06 18:14:12 |
Message-ID: | aJObdBmd9H5YAdW1@nathan |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, Aug 06, 2025 at 11:25:53PM +0900, Fujii Masao wrote:
> On Wed, Aug 6, 2025 at 1:01 PM Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com> wrote:
>> Overall, I like the change. But I have one question: should this be treated as
>> a bug fix that we back-patch to supported branches, or is it more of
>> an improvement that should only go into master?
>>
>> I reckon it might make sense to back-patch it to previous versions, as users might not upgrade always to the latest version.
>
> I understand your point. But on second thought, since the patch changes
> behavior, I'm leaning toward treating it as an improvement, so it should
> only go to master...
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.
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...)
--
nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2025-08-06 18:22:28 | Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID |
Previous Message | Adrian Klaver | 2025-08-06 18:10:55 | Re: CALL and named parameters |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-08-06 18:25:56 | Re: headerscheck warnings with late-model gcc |
Previous Message | Peter Eisentraut | 2025-08-06 18:08:40 | Re: fix ancient typo in transformRelOptions() |