On 2015/11/04 17:28, Kouhei Kaigai wrote:
>> I think we need to consider a general solution that can be applied not
>> only to the case where the component tables in a foreign join all use
>> ROW_MARK_COPY but to the case where those tables use different rowmark
>> types such as ROW_MARK_COPY and ROW_MARK_EXCLUSIVE, as I pointed out
>> upthread.
> In mixture case, FDW/CSP can choose local recheck & reconstruction based
> on the EPQ tuples of base relation. Nobody enforce FDW/CSP to return
> a joined tuple always even if author don't want to support the feature.
> Why do you think it is not a generic solution? FDW/CSP driver "can choose"
> the best solution according to its implementation and capability.
It looked to me that you were discussing only the case where component
foreign tables in a foreign join all use ROW_MARK_COPY, so I commented
that. Sorry for my misunderstanding.
Best regards,
Etsuro Fujita
