Re: Exclusion Constraints on Arrays?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Exclusion Constraints on Arrays?
Date: 2012-05-22 16:56:13
Message-ID: 3152.1337705773@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, May 22, 2012 at 12:28 PM, David E. Wheeler
> <david(at)justatheory(dot)com> wrote:
>> On May 13, 2012, at 3:45 PM, Robert Haas wrote:
>>> It seems like maybe we could work around this by remembering the
>>> contents of the pending list throughout the scan. Every time we hit a
>>> TID while scanning the main index, we check whether we already
>>> returned it from the pending list; if so, we skip it, but if not, we
>>> return it.

>> Should this go onto the To-Do list, then?

> If someone other than me can confirm that it's not a stupid approach,
> I would say yes.

It seems probably workable given that we expect the pending list to be
of fairly constrained size. However, the commit message referenced
upthread also muttered darkly about GIN's partial match logic not working
in amgettuple. I do not recall the details of that issue, but unless we
can solve that one too, there's not much use in fixing this one.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-05-22 17:09:50 Re: heap metapages
Previous Message Robert Haas 2012-05-22 16:42:53 Re: Exclusion Constraints on Arrays?