Re: cataloguing NOT NULL constraints

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: cataloguing NOT NULL constraints
Date: 2024-02-05 09:53:17
Message-ID: 202402050953.vxb2dfgzimht@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-Feb-05, Alvaro Herrera wrote:

> Subject: [PATCH v1] Fix failure to merge NOT NULL constraints in inheritance
>
> set_attnotnull() was not careful to CommandCounterIncrement() in cases
> of multiple recursion. Omission in b0e96f311985.

Eh, this needs to read "multiple inheritance" rather than "multiple
recursion". (I'd also need to describe the change for the partitioning
cases in the commit message.)

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Someone said that it is at least an order of magnitude more work to do
production software than a prototype. I think he is wrong by at least
an order of magnitude." (Brian Kernighan)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2024-02-05 10:13:41 Re: Race condition in FetchTableStates() breaks synchronization of subscription tables
Previous Message Alvaro Herrera 2024-02-05 09:50:56 Re: cataloguing NOT NULL constraints