From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Дмитрий Дегтярёв <degtyaryov(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #12946: pg_dump/pg_restore not restore data for inherit tables |
Date: | 2015-04-02 15:37:05 |
Message-ID: | 10870.1427989025@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JTQtdCz0YLRj9GA0ZHQsg==?= <degtyaryov(at)gmail(dot)com> writes:
> However, in accordance with the documentation
> http://www.postgresql.org/docs/9.4/static/ddl-inherit.html(quote: "It must
> also include check constraints with the same names and check expressions as
> those of the parent."),
> alter table t2 alter column a drop not null;
> the result must be a error.
Ah. Yeah, that's a known issue: NOT NULL constraints don't currently have
enough infrastructure for ALTER TABLE to realize whether they're inherited
or not. The system should indeed prevent you from doing DROP NOT NULL
here, but it doesn't. I think there's an item for that on the TODO list.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hale, Tyler | 2015-04-02 17:40:39 | Re: BUG #12939: GRANT ALL ON ALL SEQUENCES doesn't work for sequences not yet existing |
Previous Message | Дмитрий Дегтярёв | 2015-04-02 14:54:28 | Re: BUG #12946: pg_dump/pg_restore not restore data for inherit tables |