| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(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 18:58:04 |
| Message-ID: | 4DC8D284-05CF-4E3D-9670-AC9A32C37A36@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 22, 2012, at 9:56 AM, Tom Lane wrote:
> 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.
Well, what about a GiST operator family/class for arrays?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-05-22 19:31:08 | Re: WIP: parameterized function scan |
| Previous Message | Robert Haas | 2012-05-22 18:01:39 | Re: Add primary key/unique constraint using prefix columns of an index |