Commitf4dcaab

committed

Bugfix. The predicted_cardinality field of a plan node could be

established by previous execution of this plan in another query.

1 parentd0afdc1 commitf4dcaabCopy full SHA for f4dcaab

File tree

-1

lines changed

-1

lines changed

Lines changed: 7 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -304,7 +304,13 @@ learnOnPlanState(PlanState p, void context)`
`304`	`304`	`* to calculate produced rows. */`
`305`	`305`	`learn_rows=p->instrument->ntuples /p->instrument->nloops;`
`306`	`306`
`307`		`-if (p->plan->predicted_cardinality>0.)`
	`307`	`+/*`
	`308`	`+ * Calculate predicted cardinality.`
	`309`	`+ * We could find a positive value of predicted cardinality in`
	`310`	`+ * the case of reusing plan caused by the rewriting procedure.`
	`311`	`+ * Also it may be caused by using of a generic plan.`
	`312`	`+ */`
	`313`	`+if (p->plan->predicted_cardinality>0.&&query_context.use_aqo)`
`308`	`314`	`predicted=p->plan->predicted_cardinality;`
`309`	`315`	`elseif (IsParallelTuplesProcessing(p->plan))`
`310`	`316`	`predicted=p->plan->plan_rows*`

Comments

(0)