Re: BUG #14325: backup restore inherited constraint

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: vbv256(at)yandex(dot)ru
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14325: backup restore inherited constraint
Date: 2016-09-20 08:14:41
Message-ID: CAB7nPqS1YT_hKSXZDsVSqDf7j32ji97OeUS2Kk_Z2o8TGSxF7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.
See here for example:
https://www.postgresql.org/message-id/21633.1448383428@sss.pgh.pa.us
So this is a known limiration, and there have been some discussions
about removing this limitation in the backend, like here:
https://www.postgresql.org/message-id/CAKOSWNkN6HSyatuys8xZxzRCR-KL1OkHS5-b9qd9bf1Rad3PLA@mail.gmail.com
But there is no concrete patch lately. I don't think it would be
*that* complicated to get a rebased and polished version of what has
been proposed. It just needs care and time.

> Sorry for my bad english.

I think that's fine! And I am no native speaker either.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message kzuk 2016-09-20 10:10:51 BUG #14329: libpq doesn't send complete client certificate chain on first SSL connection
Previous Message Huan Ruan 2016-09-20 00:53:49 Re: BUG #14319: Logical decoding dropping statements in subtransactions