Re: BUG #16386: drop contraint in inherited table is missing inpg_dump backup - Mailing list pgsql-bugs

From Euler Taveira
Subject Re: BUG #16386: drop contraint in inherited table is missing inpg_dump backup
Date
Msg-id CAH503wB4v5DKG1hdjJUeBDzzWmKMFYMJRADmoW6-NfOteedF+w@mail.gmail.com
Whole thread Raw
In response to BUG #16386: drop contraint in inherited table is missing in pg_dump backup  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16386: drop contraint in inherited table is missing inpg_dump backup
List pgsql-bugs
On Fri, 24 Apr 2020 at 07:09, PG Bug reporting form <noreply@postgresql.org> wrote:

create table b (aaa int primary key,bb date );
create table A (id int primary key) inherits (B);
alter table a alter column aaa drop not null;

after i made pg_dump and pg_restore the not null contraint isexist on table
a;

It does not make sense to exclude a not null constraint on an inherited table because column "aaa" can be null in table "a" but a SELECT in table "b" will return a NULL for a primary key (ugh). It is just one of the ways to shoot yourself in the foot. If you check CREATE TABLE synopsis, there isn't NO INHERIT for not null constraints. Maybe it is worth adding a note in CREATE TABLE.


--
Euler Taveira                 http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: [BUG] non archived WAL removed during production crash recovery
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #16386: drop contraint in inherited table is missing inpg_dump backup