Re: BUG #14325: backup restore inherited constraint

From: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: vbv256(at)yandex(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14325: backup restore inherited constraint
Date: 2017-06-30 02:42:42
Message-ID: CANNMO+JCLeMaGeQ0TbnjXpMFLzGhMydybqZhO8Bi32PX1EuK8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 20, 2016 at 1:14 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:

> On Fri, Sep 16, 2016 at 3:27 PM, <vbv256(at)yandex(dot)ru> wrote:
> > If child table has field with removed inherit constraint.
> > In dump file this constraint not removed and data not restored correctly.
> > Problem also exist in PostgreSQL 9.1. Before this version appropriate
> > construction not used by me.
> >
> > -- --- to reproduce problem ----------
> > bash$ psql template1
> > template1=# create database test;
> > template1=# \c test
> >
> > [... test ...]
>
> What we ought to do here is forbid DROP NOT NULL on the table test.
>

+1 for this approach. Just encountered with the same behavior.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message K S, Sandhya (Nokia - IN/Bangalore) 2017-06-30 09:41:34 Postgres process invoking exit resulting in sh-QUIT core
Previous Message Sergey Koposov 2017-06-29 19:56:02 Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow