Re: [PATCH] Deferrable unique constraints vs join removal -- bug? - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: [PATCH] Deferrable unique constraints vs join removal -- bug?
Date
Msg-id CABRT9RCToTUvuaX0p+voWcCzaJ-q0NcRm-AQikQYHB+iEXbkRA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Deferrable unique constraints vs join removal -- bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Deferrable unique constraints vs join removal -- bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Oct 23, 2011 at 06:44, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I think maybe what we should do is add
>> an "immediate" field to IndexOptInfo, mirroring the existing unique
>> flag, and have get_relation_info() populate it from indimmediate, and
>> then make relation_has_unique_index() disqualify any non-immediate
>> index.
>
> Yeah, this seems like the right fix.

Oh, that sounds pretty obvious now that you mention it. :)

I will try to come up with a new patch in a few days (haven't had too
much time lately).

Regards,
Marti


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Review: [PL/pgSQL] %TYPE and array declaration - second patch
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Deferrable unique constraints vs join removal -- bug?