Re: patch for check constraints using multiple inheritance - Mailing list pgsql-hackers

From Robert Haas
Subject Re: patch for check constraints using multiple inheritance
Date
Msg-id AANLkTim9wRSqZoar9tCyqfbagnXQrKHM0oD8Z2u-WQh9@mail.gmail.com
Whole thread Raw
In response to Re: patch for check constraints using multiple inheritance  (Yeb Havinga <yebhavinga@gmail.com>)
Responses Re: patch for check constraints using multiple inheritance
List pgsql-hackers
On Mon, Aug 2, 2010 at 2:56 PM, Yeb Havinga <yebhavinga@gmail.com> wrote:
> I do not completely understand what you mean with the destruction of
> reusability of ATOneLevelRecursion, currently only called by ATPrepAddColumn
> - in the patch it is documented in the definition of relVisited that is it
> visit info for each subcommand. The loop over subcommands is in
> ATController, where the value is properly reset for each all current and
> future subcommands. Hence the ATOneLevelRecursion routing is usable in its
> current form for all callers during the prep stage, and not only
> ATPrepAddColumn.

Well, only if they happen to want the "visit each table only once"
behavior, which might not be true for every command type.

>> I am of the opinion that the chances of a unifying solution popping up
>> are pretty much zero.  :-)
>
> Me too, now I understand the fixes must be in the execution stages.

OK.  I'll go ahead and commit the patch upthread, so that the
constraint bug is fixed, and then we can keep arguing about what do
about the column bug, perhaps on a new thread.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: lock_timeout GUC patch - Review
Next
From: Robert Haas
Date:
Subject: Re: multibyte charater set in levenshtein function