From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tender Wang <tndrwang(at)gmail(dot)com> |
Subject: | Re: not null constraints, again |
Date: | 2024-10-10 06:30:32 |
Message-ID: | CACJufxG=M-8kY-9LmapFWipS8LzYoheBR+r58z_=kJmvT59sew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
tricky case:
drop table if exists part, part0 cascade;
create table part (a int not null) partition by range (a);
create table part0 (a int primary key);
alter table part attach partition part0 for values from (0) to (1000);
alter table ONLY part add primary key(a);
alter table ONLY part drop constraint part_a_not_null;
-- alter table ONLY part alter column a drop not null;
Now we are in a state where a partitioned
table have a primary key but doesn't have a not-null constraint for it.
select indisunique, indisprimary, indimmediate,indisvalid
from pg_index
where indexrelid = 'part_pkey'::regclass;
shows this primary key index is invalid.
but
select conname,contype,convalidated
from pg_constraint where conname = 'part_pkey';
shows this primary key constraint is valid.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-10-10 06:39:17 | Re: Wrong results with grouping sets |
Previous Message | Masahiko Sawada | 2024-10-10 06:25:24 | Re: Testing autovacuum wraparound (including failsafe) |