<div dir="ltr">If we are going to change that portion of the code, we may as well go a bit forward and allow any
expressionsto be fetched from a foreign server (obviously, if that server is capable of doing so). It will help, when
wecome to aggregate push-down or whole query push-down (whenever that happens). So, instead of attr_needed, which
restrictsonly the attributes to be fetched, why not to targetlist itself?<br /></div><div class="gmail_extra"><br /><br
/><divclass="gmail_quote">On Mon, Jun 30, 2014 at 7:18 PM, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us"target="_blank">tgl@sss.pgh.pa.us</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Etsuro Fujita
<<ahref="mailto:fujita.etsuro@lab.ntt.co.jp">fujita.etsuro@lab.ntt.co.jp</a>> writes:<br /> > Done. I think
thisis because create_foreignscan_plan() makes reference<br /> > to attr_needed, which isn't computed for
inheritancechildren.<br /><br /></div>I wonder whether it isn't time to change that. It was coded like that<br />
originallyonly because calculating the values would've been a waste of<br /> cycles at the time. But this is at least
thethird place where it'd be<br /> useful to have attr_needed for child rels.<br /><br />
regards,tom lane<br /></blockquote></div><br /><br clear="all" /><br />-- <br /><div dir="ltr">Best Wishes,<br
/>AshutoshBapat<br />EnterpriseDB Corporation<br />The Postgres Database Company<br /></div></div>