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

>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
Tom> BTW, the reason we need to store the column count explicitly isTom> that we have to ignore the added columns if a
compositetype hasTom> had an ADD COLUMN done to it since the RTE was made.  TheTom> submitted patch fails rather
nastilyin such cases, if theTom> composite type isn't last in the function list.
 

Am I understanding correctly that the only reason this didn't fail
before we added ORDINALITY is that the executor in general does not
care if there are more columns in a tuple than it expects? And that
adding ORDINALITY broke this already?

-- 
Andrew (irc:RhodiumToad)