Message-ID: <4EB83BF7.4070905@gmail.com>
Date: Mon, 07 Nov 2011 15:13:43 -0500
From: Jay Levitt <jay.levitt@gmail.com>
User-Agent: Postbox 3.0.1 (Macintosh/20111102)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-performance@postgresql.org
Subject: Re: Predicates not getting pushed into SQL function?
References: <4EB2D3CB.7020708@gmail.com> <6646.1320345676@sss.pgh.pa.us>
	<4EB2E251.90906@gmail.com> <11061.1320352516@sss.pgh.pa.us>
In-Reply-To: <11061.1320352516@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
 > Please don't send HTML-only email to these lists.

Oops - new mail client, sorry.

 > Anyway, the answer seems to be that inline_set_returning_function needs
 > some work to handle cases with declared OUT parameters.  I will see
 > about fixing that going forward, but in existing releases what you need
 > to do is declare the function as returning SETOF some named composite
 > type


Yes, that patch works great!  Oddly enough, the workaround now does NOT 
work; functions returning SETOF named composite types don't get inlined, but 
functions returning the equivalent TABLE do get inlined.  Let me know if you 
need a failcase, but the bug doesn't actually affect me now :)

Jay

 >
 > create type matcher_result as (user_id int, match int);
 >
 > create or replace function matcher() returns setof matcher_result as ...