Re: pg17 issues with not-null contraints - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg17 issues with not-null contraints
Date
Msg-id 202404161811.rv6b7vnmt3en@alvherre.pgsql
Whole thread Raw
In response to Re: pg17 issues with not-null contraints  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: pg17 issues with not-null contraints
Re: pg17 issues with not-null contraints
List pgsql-hackers
On 2024-Apr-15, Alvaro Herrera wrote:

> - Fourth thought: we do as in the third thought, except we also allow
> DROP CONSTRAINT a constraint that's marked "local, inherited" to be
> simply an inherited constraint (remove its "local" marker).

Here is an initial implementation of what I was thinking.  Can you
please give it a try and see if it fixes this problem?  At least in my
run of your original test case, it seems to work as expected.

This is still missing some cleanup and additional tests, of course.
Speaking of which, I wonder if I should modify pg16's tests so that they
leave behind tables set up in this way, to immortalize pg_upgrade
testing.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_combinebackup fails on file named INCREMENTAL.*
Next
From: Andres Freund
Date:
Subject: Re: documentation structure