| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Constraint merge and not valid status |
| Date: | 2016-07-21 15:38:17 |
| Message-ID: | CA+TgmoY_eFrN1qve50=rzoFKzvGCRic=KDVgfnS2detU8QK7sg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 13, 2016 at 5:22 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Consider a scenario where one adds a *valid* constraint on a inheritance
> parent which is then merged with a child table's *not valid* constraint
> during inheritance recursion. If merged, the constraint is not checked
> for the child data even though it may have some. Is that an oversight?
Seems like it. I'd recommend we just error out in that case and tell
the user that they should validate the child's constraint first.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2016-07-21 15:42:46 | fixes for the Danish locale |
| Previous Message | Teodor Sigaev | 2016-07-21 15:20:37 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |