Horton

Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Suraj Kharage <suraj.kharage@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-11-15T03:15:39Z
Lists: pgsql-hackers 
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?

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. Small fixes for Add ALTER TABLE ... ALTER CONSTRAINT ... SET [NO] INHERIT

  2. Add ALTER TABLE ... ALTER CONSTRAINT ... SET [NO] INHERIT

  3. Add pg_constraint rows for not-null constraints