On 2016-06-03 22:07:21 +0000, Tom Lane wrote:
> Also add a regression test case exercising the same scenario for
> FunctionScan. That's not broken right now, because the function's
> result will get shoved into a tuplestore between generation and use;
> but it could easily become broken whenever we get around to optimizing
> FunctionScan better.
Indeed, I just locally broke that for a few minutes. Thanks for that.
