Horton

Re: alter table only ... drop constraint broken in HEAD

Greg Stark <stark@mit.edu>

View thread
From: Greg Stark <stark@mit.edu>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-10-09T15:17:45Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Avoid having two copies of the HOT-chain search logic.

On Fri, Oct 7, 2011 at 5:45 PM, Alex Hunsaker <badalex@gmail.com> wrote:
> If I find the time maybe Ill submit something along these lines for
> the next commit fest.
>

So i just picked up the non-inherited constraints patch and quickly
ran into the same problem and found this thread.

I think it makes sense to hold off on this patch until these issues
are resolved. Because we really do need to test the cases when adding
or removing child tables that have constraints with the same name as
non-inherited parent tables. And I'm not sure what will happen in
these cases once these issues are resolved.



-- 
greg