Re: Problem identifying constraints which should not be inherited

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Chris Fischer" <Chris(dot)Fischer(at)channeladvisor(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problem identifying constraints which should not be inherited
Date: 2008-03-19 14:53:22
Message-ID: 1430.1205938402@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

NikhilS <nikkhils(at)gmail(dot)com> writes:
> On Fri, Mar 7, 2008 at 6:37 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Added to TODO:
>> o Require all CHECK constraints to be inherited

> PFA, a small patch attached which should fix this.

If it's a small patch, it's wrong by definition. AFAICS there is no way
to fix this correctly that doesn't involve catalog changes. The point
of the TODO is that you have to enforce that the inherited constraint
sticks around, eg can't be dropped on a child table while it's still
present on the parent. There are implications for pg_dump too.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Rui Martins 2008-03-19 15:43:38 Re: BUG #4044: Incorrect RegExp substring Output
Previous Message Tom Lane 2008-03-19 14:43:59 Re: BUG #4044: Incorrect RegExp substring Output

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-19 15:10:26 Re: Multiple SRF right after SELECT
Previous Message Volkan YAZICI 2008-03-19 13:08:53 Re: Multiple SRF right after SELECT