Re: alter table only ... drop constraint broken in HEAD - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: alter table only ... drop constraint broken in HEAD
Date
Msg-id CAFaPBrTE-rn51bi0Mbx1pOuRqX1K5T4k9Keu8PqjMDoeiExdNg@mail.gmail.com
Whole thread Raw
In response to Re: alter table only ... drop constraint broken in HEAD  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: alter table only ... drop constraint broken in HEAD
List pgsql-hackers
On Fri, Oct 7, 2011 at 09:50, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Oct 7, 2011 at 11:19 AM, Alex Hunsaker <badalex@gmail.com> wrote:
>> My only thought is
>> perhaps we should add that missing unique index on (conrelid,
>> conname). If we are not going to support duplicate names in the code,
>> we might as well enforce it. No?
>
> Not sure.  There could be performance or other ramifications to that.
> For now I'm more interested in fixing this particular bug than I am in
> getting into a wider world of re-engineering...

Yeah, looking at the code a bit closer we would also want to fix
various places to take advantage of the index. Seems like it could be
a big win when you have thousands of constraints (albeit only in the
add/drop case).

If I find the time maybe Ill submit something along these lines for
the next commit fest.

Thanks!


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: PQsendQuery/ PQgetResult Problem
Next
From: Alex Hunsaker
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.