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

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

            regards, tom lane



pgsql-hackers by date:

Previous
From: John H
Date:
Subject: Re: Making pg_rewind faster
Next
From: Tom Lane
Date:
Subject: Re: Cross-type index comparison support in contrib/btree_gin