| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pinker <pinker(at)onet(dot)eu>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: pg_dump - wrong order with inheritance |
| Date: | 2016-06-15 08:03:28 |
| Message-ID: | CAB7nPqSqVbfXwsyggg-b7rO=jR4sihY7K2hN9x8U1ngTbUJRzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 25, 2015 at 1:43 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This is a known limitation of the backend. It should refuse to let you
> DROP NOT NULL in a case where the NOT NULL is an inherited constraint,
> as it is here. It would not let you drop a CHECK constraint in an
> equivalent situation; but the NOT NULL support is older/more primitive
> and currently doesn't do enough bookkeeping to realize that a03's NOT NULL
> constraint is inherited from a parent table. Fixing that is on our to-do
> list, but it hasn't been very high priority.
Just an update for pinker: I have posted a patch here to address the
problem in the next major releases, 10.0 presumably:
https://www.postgresql.org/message-id/CAB7nPqTPXgX9HiyhhtAgpW7jbA1iskMCSoqXPEEB_KYXYy1E1Q@mail.gmail.com
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | buschmann | 2016-06-15 08:27:14 | BUG #14192: pg_dump/pg_restore omit setting search_path in restored db |
| Previous Message | Gabriele Monfardini | 2016-06-15 07:45:13 | Re: BUG #14188: "FOR SELECT DISTINCT, ORDER BY expressions must appear IN SELECT list" error and table alias |