mirror of https://github.com/citusdata/citus.git
8efca3b60a
Use short lived per-tuple context in citus_evaluate_expr like (pg) evaluate_expr does. We should not use planState->ExprContext when evaluating expressions as it might lead to freeing the same executor twice (first one happens in citus_evaluate_expr itself and the other one happens when postgres doing clean-up for the top level executor state), which in turn might cause seg.faults. However, now as we don't have necessary planState info to evaluate prepared statements, we also add planState->es_param_list_info to per-tuple ExprContext. |
||
|---|---|---|
| .. | ||
| backend | ||
| include | ||
| test | ||