Re: [PATCH] Deferrable unique constraints vs join removal -- bug?

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Deferrable unique constraints vs join removal -- bug?
Date: 2011-10-23 18:12:51
Message-ID: CABRT9RCToTUvuaX0p+voWcCzaJ-q0NcRm-AQikQYHB+iEXbkRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 23, 2011 at 06:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-10-23 18:39:40 Re: [PATCH] Deferrable unique constraints vs join removal -- bug?
Previous Message Pavel Stehule 2011-10-23 17:33:56 Review: [PL/pgSQL] %TYPE and array declaration - second patch