Horton
Menu

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>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Michael Paquier <michael@paquier.xyz>, Ali Akbar <the.apaan@gmail.com>, Michael Paquier <michael.paquier@gmail.com>, tushar <tushar.ahuja@enterprisedb.com>, pgsql-hackers@postgresql.org, rmt@lists.postgresql.org
Date: 2025-07-04T17:37:11Z
Lists: pgsql-hackers 
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2025-Jul-04, Alvaro Herrera wrote:
>> Hmm, crake doesn't like the fact that there's no regnamespace in 9.4.
>> Apparently in version 13 we claim to support back to 9.0.  I only tried
>> with an old server version 12.  Should be an easy fix ...

> It goes like this.  It's tested with 9.2 only though, as 9.1 doesn't
> compile from Git (lack of Flex) and I didn't want to try a tarball.

Query works, or at least throws no error, back to 8.4 (the oldest I
have at hand).

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix new pg_upgrade query not to rely on regnamespace

  2. pg_upgrade: check for inconsistencies in not-null constraints w/inheritance

  3. Apply ALTER ... SET NOT NULL recursively in ALTER ... ADD PRIMARY KEY.