Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
>> Is physical_tlist optimization sensible for RecursiveScan? We seem
>> to use it for every other Scan node type.
> To enable physical_tlist optimization, it seems build_physical_tlist,
> use_physical_tlist and disuse_physical_tlist need to be
> changed. build_physical_tlist and use_physical_tlist have been already
> patched and only disuse_physical_tlist needs to be patched. Any other
> place I miss to enable the optimization?
IIRC, the comment for build_physical_tlist hadn't been patched, but
yeah that seems like about it.
regards, tom lane