Feedback-ID: ia2694551:Fastmail
Date: Thu, 18 Apr 2024 15:39:12 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andrew Bille <andrewbille@gmail.com>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, 
	Peter Eisentraut <peter@eisentraut.org>, Robert Haas <robertmhaas@gmail.com>, 
	pgsql-hackers@lists.postgresql.org
Subject: Re: cataloguing NOT NULL constraints
Message-ID: <202404181339.ql3wlpryz6kw@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJnzarwkfRu76_yi3dqVF_WL-MpvT54zMwAxFwJceXdHB76bOA@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202404181339.ql3wlpryz6kw%40alvherre.pgsql>
Precedence: bulk

On 2024-Jan-25, Andrew Bille wrote:

> Starting from b0e96f31, pg_upgrade fails with inherited NOT NULL constraint:
> For example upgrade from 9c13b6814a (or REL_12_STABLE .. REL_16_STABLE) to
> b0e96f31 (or master) with following two tables (excerpt from
> src/test/regress/sql/rules.sql)
> 
> create table test_0 (id serial primary key);
> create table test_1 (id integer primary key) inherits (test_0);

I have pushed a fix which should hopefully fix this problem
(d9f686a72e).  Please give this a look.  Thanks for reporting the issue.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"I apologize for the confusion in my previous responses.
 There appears to be an error."                   (ChatGPT)