From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | frankpit(at)pop(dot)dn(dot)net |
Cc: | wieck(at)debis(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Function-manager redesign: second draft (long) |
Date: | 1999-10-31 02:29:39 |
Message-ID: | m11hkkW-0003kLC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bernie Franpitt wrote:
> SELECT * FORM t WHERE t.object <intersects> pts;
>
> Under these circumstances it would be really nice to be able to pass a
> set of objects (as an SPI tuple table for instance) into the index.
>
> Currently, the way I do this (with a custom access method) is to create
> a temp table, put the key set into the temp table, and pass the name of
> the temp table to the access method in the search key. The access
> method then does an SPI select on the temp table and stores the returned
> items into the private scan state for use during the scan.
>
> While I realize that implementing this example requires much more than a
> change to the function interface, I hope that it illustrates that it is
> perhaps a good idea to keep as much flexibility in the function
> interface as possible.
Uhhh - it is a good idea, but passing tuple sets as arguments
to functions, that will cause headaches, man.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-10-31 05:54:45 | Re: [HACKERS] pgaccess for 6.5.3 |
Previous Message | Bruce Momjian | 1999-10-31 02:05:26 | Re: [HACKERS] missing mugshotsu |