Re: BUG #14325: backup restore inherited constraint
От | Michael Paquier |
---|---|
Тема | Re: BUG #14325: backup restore inherited constraint |
Дата | |
Msg-id | CAB7nPqS1YT_hKSXZDsVSqDf7j32ji97OeUS2Kk_Z2o8TGSxF7g@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #14325: backup restore inherited constraint (vbv256@yandex.ru) |
Ответы |
Re: [BUGS] BUG #14325: backup restore inherited constraint
|
Список | pgsql-bugs |
On Fri, Sep 16, 2016 at 3:27 PM, <vbv256@yandex.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
В списке pgsql-bugs по дате отправления: