Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors
Date
Msg-id CAB7nPqRKhXy3BzDkAAXnpM_izqcNNPhtaNS=aOxLySx7qfX67A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Fri, Oct 2, 2015 at 3:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> swingi@gmail.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

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: GRANT USAGE ON SEQUENCE missing from psql command completion
Next
From: Michael Paquier
Date:
Subject: Re: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors