Request a Demo
Home   >   mailing lists

Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
Date
Msg-id CA+TgmobhYw5=GzGUcsNvb_FtS=PT4EsA3kNNJK-Sh6WyFx=WmQ@mail.gmail.com
Whole thread Raw
Responses Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
List pgsql-hackers
Tree view
On Thu, Nov 14, 2024 at 12:02 AM Suraj Kharage <suraj.kharage@enterprisedb.com> wrote:
Alvaro stated that allowing a not null constraint state to be modified from INHERIT to NO INHERIT is going to be quite problematic because of the number of weird cases to avoid, so for now that support is not added.

What's the reasoning behind that restriction? What are the weird cases? 

--

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Skip collecting decoded changes of already-aborted transactions
Next
From: Amit Kapila
Date:
Subject: Re: logical replication: restart_lsn can go backwards (and more), seems broken since 9.4