Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: 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>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2023-09-29T00:16:35Z
Lists: pgsql-hackers
On Thu, Sep 28, 2023 at 01:29:21PM -0500, Justin Pryzby wrote: > On Thu, Dec 14, 2017 at 07:18:59PM +0700, Ali Akbar wrote: > > By the way, should i add this patch to the current commitfest? > > The patch for pg_upgrade --check got forgotten 6 years ago, but it's a > continuing problem (we hit it again which cost an hour during > pg_upgrade) and ought to be (have been) backpatched. You mean when upgrading from an instance of 9.6 or older as c30f177 is not there, right? With the new project policy to support pg_upgrade for 10 years, there's still a very good argument for backpatching a pre-check down to v11. Anyway, it seems like the patch from [1] has no need to run this check when the old cluster's version is 10 or newer. And perhaps it should mention that this check could be removed from pg_upgrade once v10 support is out of scope, in the shape of a comment. > I didn't dig into it, but maybe it'd even be possible to fix the issue > with ALTER..DROP NOT NULL ... Interesting point. I haven't checked either. [1]: https://postgr.es/m/CACQjQLqoXTzCV4+-s1XOT62tY8ggkZkH4kY03gm2aQYOMXE+SA@mail.gmail.com -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix new pg_upgrade query not to rely on regnamespace
- f943e2339f6c 16.10 landed
- bd48455d88a8 15.14 landed
- bcb8d47cdd5e 17.6 landed
- 94dc2b37baee 14.19 landed
- 708469281ea8 13.22 landed
- 1e007722fa86 18.0 landed
- 144ad723a448 19 (unreleased) landed
-
pg_upgrade: check for inconsistencies in not-null constraints w/inheritance
- f63e408e894c 16.10 landed
- f295494d338c 19 (unreleased) landed
- ea3386cc784a 14.19 landed
- b8b2e60527c6 17.6 landed
- b0f0e2221f42 13.22 landed
- 0f49586850a9 15.14 landed
- 07da2985d6bf 18.0 landed
-
Apply ALTER ... SET NOT NULL recursively in ALTER ... ADD PRIMARY KEY.
- c30f1770a93d 10.0 landed