This case fails in regression. Preliminary investigations suggest that this is due to SQL function execution on a datanode where it fails to find matching rows because of different distribution strategies for different tables.
/Users/pavan/work/SOURCES/postgres-xl/src/test/regress/expected/misc.out Mon Dec 1 15:21:27 2014
--- /Users/pavan/work/SOURCES/postgres-xl/src/test/regress/results/misc.out Mon Dec 1 15:24:30 2014***
465,476 ****
-- everyone else does nothing.
--
SELECT p.name, name(p.hobbies) FROM ONLY person p ORDER BY 1,2;
! name | name
! -------+-------------
! joe | basketball
! mike | posthacking
! sally | basketball
! (3 rows)
--
-- as above, but jeff also does post_hacking.
--- 465,474 ----
-- everyone else does nothing.
--
SELECT p.name, name(p.hobbies) FROM ONLY person p ORDER BY 1,2;
! name | name
! ------+-------------
! mike | posthacking
! (1 row)
--
-- as above, but jeff also does post_hacking.