Re: UNNEST with multiple args, and TABLE with multiple funcs

>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
Tom> I've committed this patch after some significant editorialization, butTom> leaving the use of TABLE( ... ) syntax
in-place. If we decide that weTom> don't want to risk doing that, we can change to some other syntax later.
 

Is this intended:

create function foo() returns setof footype language plpgsql as $f$ begin return next row(1,true); end; $f$;

select pg_typeof(f), row_to_json(f) from foo() with ordinality f(p,q);pg_typeof |           row_to_json           
-----------+---------------------------------record    | {"p":1,"q":true,"ordinality":1}
(1 row)

select pg_typeof(f), row_to_json(f) from foo() f(p,q);pg_typeof |   row_to_json    
-----------+------------------footype   | {"a":1,"b":true}
(1 row)

-- 
Andrew (irc:RhodiumToad)