Downloads
Home   >   mailing lists

Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL
Date
Msg-id 202507041621.fs23x5filgko@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL
List pgsql-hackers
Tree view 
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)

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7