From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows |
Date: | 2008-10-14 21:24:38 |
Message-ID: | b42b73150810141424ob8c157eq99040695968f75de@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 14, 2008 at 10:59 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
>> Here is another use-case solved by the patch. Previously, there was
>> no easy way to index on a composite function result. The following
>> works in HEAD:
>
>> create function func(f foo, a out int, b out int) returns record ...
>
>> create index foo_idx on foo(func(foo));
>
> Urk ... "works" for small values of "work", perhaps. Did you try using
> the index from a fresh session?
>
> We could support this for named composite types but not for anonymous
> record types. I'm not quite sure how to enforce that distinction
> considering that the opclass is defined to take "record". Maybe we
> should apply CheckAttributeType() to index column types?
yup. being able to do this with anonymous types would be nice
though...put a thumbtack on that :-)
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2008-10-14 21:25:36 | Re: spoonbill is failing citext test |
Previous Message | Andrew Dunstan | 2008-10-14 21:17:55 | Re: spoonbill is failing citext test |