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

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

On Sun, Oct 9, 2011 at 1:56 PM, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
>> 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?

Yeah, I've just been mostly AFK for ~53 hours. It's committed now.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-10-10 04:09:13 Re: SET variable - Permission issues
Previous Message Alex Goncharov 2011-10-10 02:39:17 Re: What is known about PostgreSQL HP-UX support?