From: Amit Langote <amitlangot...@gmail.com> > Okay, so maybe not moving the whole logic into the FDW's > BeginForeignModify(), but at least if we move this... > > @@ -441,6 +449,72 @@ ExecInsert(ModifyTableState *mtstate, > + /* > + * Determine if the FDW supports batch insert and determine the > batch > + * size (a FDW may support batching, but it may be disabled for the > + * server/table). Do this only once, at the beginning - we don't want > + * the batch size to change during execution. > + */ > + if (resultRelInfo->ri_FdwRoutine->GetForeignModifyBatchSize && > + resultRelInfo->ri_FdwRoutine->ExecForeignBatchInsert && > + resultRelInfo->ri_BatchSize == 0) > + resultRelInfo->ri_BatchSize = > + > resultRelInfo->ri_FdwRoutine->GetForeignModifyBatchSize(resultRelInfo); > > ...into ExecInitModifyTable(), ExecInsert() only needs the following block:
Does ExecInitModifyTable() know all leaf partitions where the tuples produced by VALUES or SELECT go? ExecInsert() doesn't find the target leaf partition for the first time through the call to ExecPrepareTupleRouting()? Leaf partitions can have different batch_size settings. Regards Takayuki Tsunakawa
