Feedback-ID: ia2694551:Fastmail
Date: Fri, 4 Jul 2025 18:21:31 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>,
	Michael Paquier <michael@paquier.xyz>, Ali Akbar <the.apaan@gmail.com>,
	Michael Paquier <michael.paquier@gmail.com>,
 Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
	tushar <tushar.ahuja@enterprisedb.com>, pgsql-hackers@postgresql.org,
 rmt@lists.postgresql.org
Subject: Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in
 child table must be marked NOT NULL
Message-ID: <202507041621.fs23x5filgko@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4084943.1751573241@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/202507041621.fs23x5filgko%40alvherre.pgsql>
Precedence: bulk

On 2025-Jul-03, Tom Lane wrote:

> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > On 2025-Jul-03, Justin Pryzby wrote:
> >>> Actually I think we should consider backporting to all live versions
> 
> >> If you don't backpatch it, there's no point.
> 
> > Oh yeah, you're absolutely right.
> 
> No, it'd still be useful for handling upgrades from $busted_version
> to current.  But it seems also useful in the back branches, so
> +1 for back-patch.

Pushed to all branches.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)