Re: patch for check constraints using multiple inheritance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yeb Havinga <yebhavinga(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Henk Enting <h(dot)d(dot)enting(at)mgrid(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: patch for check constraints using multiple inheritance
Date: 2010-07-30 15:39:10
Message-ID: 19676.1280504350@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Yeb Havinga <yebhavinga(at)gmail(dot)com> writes:
> Regard the following lattice (direction from top to bottom):

> 1
> |\
> 2 3
> \|\
> 4 5
> \|
> 6

> When adding a constraint to 1, the proper coninhcount for that
> constraint on relation 6 is 2. But the code currently counts to 3, since
> 6 is reached by paths 1-2-4-5, 1-3-4-6, 1-3-5-6.

Mph. I'm not sure that 3 is wrong. You have to consider what happens
during a DROP CONSTRAINT, which as far as I saw this patch didn't
address.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-07-30 15:48:40 Re: patch for check constraints using multiple inheritance
Previous Message Robert Haas 2010-07-30 15:35:07 Re: patch for check constraints using multiple inheritance