RE: ADD/DROP CONSTRAINT and inheritance - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject RE: ADD/DROP CONSTRAINT and inheritance
Date
Msg-id ECEHIKNFIMMECLEBJFIGAEKCCAAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: ADD/DROP CONSTRAINT and inheritance  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ADD/DROP CONSTRAINT and inheritance  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> > I'm not sure what you mean here, Tom - I meant that the ONLY
> keyword could
> > be optional.
>
> The current gram.y code allows either ALTER TABLE foo ONLY or ALTER
> TABLE foo* for all forms of ALTER ... with the default interpretation
> being the latter.

Oops - ok, I didn't notice that...hmmm...maybe I should check my patch for
that before Bruce commits it...

> > At the moment we have:
> > * ADD CONSTRAINT does not propagate
>
> I doubt you will find anyone who's willing to argue that that's not a
> bug --- specifically, AlterTableAddConstraint()'s lack of inheritance
> recursion like its siblings have.  Feel free to fix it.

It was next on my list.  However, I don't want to step on Stephan's toes...

Chris



pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Plans for solving the VACUUM problem
Next
From: Tom Lane
Date:
Subject: Re: More pgindent follies