| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | swingi(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors |
| Date: | 2015-10-01 23:21:59 |
| Message-ID: | CAB7nPqRKhXy3BzDkAAXnpM_izqcNNPhtaNS=aOxLySx7qfX67A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 2, 2015 at 3:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> swingi(at)gmail(dot)com writes:
>> I just noticed that when you add a not valid constraint to a table that is
>> inherited, this will result in pg_dump emitting an add constraint operation
>> for every table in the inheritance hierarchy. Therefore restoring a dump
>> will cause errors. Below is an example, first with a valid constraint (goes
>> well), and then the not valid constraint.
>
> Seems to be a simple oversight in the code for handling not-valid
> constraints. Thanks for the report!
Tom, are you working on a fix? I began looking at it a bit when this
has been posted FWIW so I could post a patch except that I run out of
fuel yesterday :)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-10-01 23:23:00 | Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors |
| Previous Message | Thomas Munro | 2015-10-01 19:41:16 | Re: GRANT USAGE ON SEQUENCE missing from psql command completion |