Re: Foreign join pushdown vs EvalPlanQual - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Foreign join pushdown vs EvalPlanQual
Date
Msg-id 5614BE25.10105@lab.ntt.co.jp
Whole thread Raw
In response to Re: Foreign join pushdown vs EvalPlanQual  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Foreign join pushdown vs EvalPlanQual  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On 2015/10/07 15:06, Kyotaro HORIGUCHI wrote:
> At Wed, 7 Oct 2015 00:24:57 -0400, Robert Haas <robertmhaas@gmail.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




pgsql-hackers by date:

Previous
From: Pallavi Sontakke
Date:
Subject: [PATCH] Documentation bug in 9.5/ master - pg_replication_origin_session_setup
Next
From: Michael Paquier
Date:
Subject: Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members