From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, robertmhaas(at)gmail(dot)com |
Cc: | kaigai(at)ak(dot)jp(dot)nec(dot)com, pgsql-hackers(at)postgresql(dot)org, shigeru(dot)hanada(at)gmail(dot)com |
Subject: | Re: Foreign join pushdown vs EvalPlanQual |
Date: | 2015-10-07 06:39:33 |
Message-ID: | 5614BE25.10105@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015/10/07 15:06, Kyotaro HORIGUCHI wrote:
> At Wed, 7 Oct 2015 00:24:57 -0400, Robert Haas <robertmhaas(at)gmail(dot)com> wrote
>> I think it rather requires *replacing* two resjunk columns by one new
>> one. The whole-row references for the individual foreign tables are
>> only there to support EvalPlanQual; if we instead have a column to
>> populate the foreign scan's slot directly, then we can use that column
>> for that purpose directly and there's no remaining use for the
>> whole-row vars on the baserels.
> It is what I had in mind.
OK I'll investigate this further.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-10-07 07:07:40 | Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members |
Previous Message | Pallavi Sontakke | 2015-10-07 06:38:26 | [PATCH] Documentation bug in 9.5/ master - pg_replication_origin_session_setup |