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

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: alter table only ... drop constraint broken in HEAD
Date: 2011-10-09 17:56:08
Message-ID: CAFaPBrQiQorDDHrA6e+0CW62Be61ThTgvhPZq41O8HbPdPfNuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 9, 2011 at 09:17, Greg Stark <stark(at)mit(dot)edu> wrote:
> On Fri, Oct 7, 2011 at 5:45 PM, Alex Hunsaker <badalex(at)gmail(dot)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.

Doesn't someone just need to commit Roberts patch? I suppose it could
do with a better review than my eyeballing... Maybe thats where the
hang up is?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jun Ishiduka 2011-10-09 18:04:25 Re: Online base backup from the hot-standby
Previous Message Florian Pflug 2011-10-09 17:10:23 Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable