Allow parallel query for prepared statements with generic plans.
authorRobert Haas <rhaas@postgresql.org>
Fri, 27 Oct 2017 20:22:39 +0000 (22:22 +0200)
committerRobert Haas <rhaas@postgresql.org>
Fri, 27 Oct 2017 20:22:39 +0000 (22:22 +0200)
commit682ce911f8f30de39b13cf211fc8ceb8c6cbc01b
tree36caf44ee3d2da6af8fef9b9366ff4432e7ea91b
parent6784d7a1dc69d53b7f41eebf62bf7ffd63885294
Allow parallel query for prepared statements with generic plans.

This was always intended to work, but due to an oversight in
max_parallel_hazard_walker, it didn't.  In testing, we missed the
fact that it was only working for custom plans, where the parameter
value has been substituted for the parameter itself early enough
that everything worked.  In a generic plan, the Param node survives
and must be treated as parallel-safe.  SerializeParamList provides
for the transmission of parameter values to workers.

Amit Kapila with help from Kuntal Ghosh.  Some changes by me.

Discussion: http://postgr.es/m/CAA4eK1+_BuZrmVCeua5Eqnm4Co9DAXdM5HPAOE2J19ePbR912Q@mail.gmail.com
src/backend/optimizer/util/clauses.c
src/pl/plpgsql/src/pl_exec.c
src/test/regress/expected/select_parallel.out
src/test/regress/sql/select_parallel.sql