Re: [HACKERS] Progress report: buffer refcount bugs and SQL functions

From: wieck(at)debis(dot)com (Jan Wieck)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: wieck(at)debis(dot)com, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Progress report: buffer refcount bugs and SQL functions
Date: 1999-09-23 15:28:51
Message-ID: m11UAnj-0003kzC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>
> wieck(at)debis(dot)com (Jan Wieck) writes:
> > Tom Lane wrote:
>
> What we really need to make functions-returning-sets work properly is
> an implementation somewhat like aggregate functions. We need to make
> a list of all the Iter nodes present in a targetlist and cycle through
> the values returned by each in a methodical fashion (run the rightmost
> through its full cycle, then advance the next-to-rightmost one value,
> run the rightmost through its cycle again, etc etc). Also there needs
> to be an understanding of the hierarchy when an Iter appears in the
> arguments of another Iter's function. (You cycle the upper one for
> *each* set of arguments created by cycling its sub-Iters.)

Shouldn't a function returning a SET of tuples cause a proper
join?

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) #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-09-23 15:31:04 Re: [HACKERS] Progress report: buffer refcount bugs and SQL functions
Previous Message Jan Wieck 1999-09-23 15:13:19 Re: [HACKERS] Problem with new function