Flush Memoize cache when non-key parameters change
authorDavid Rowley <drowley@postgresql.org>
Wed, 24 Nov 2021 01:56:18 +0000 (14:56 +1300)
committerDavid Rowley <drowley@postgresql.org>
Wed, 24 Nov 2021 01:56:18 +0000 (14:56 +1300)
commit1050048a315790a505465bfcceb26eaf8dbc7e2e
tree86093353545d96b85123fb067415854eaae36549
parente502150f7d0be41e3c8784be007fa871a32d8a7f
Flush Memoize cache when non-key parameters change

It's possible that a subplan below a Memoize node contains a parameter
from above the Memoize node.  If this parameter changes then cache entries
may become out-dated due to the new parameter value.

Previously Memoize was mistakenly not aware of this.  We fix this here by
flushing the cache whenever a parameter that's not part of the cache
key changes.

Bug: #17213
Reported by: Elvis Pranskevichus
Author: David Rowley
Discussion: https://postgr.es/m/17213-988ed34b225a2862@postgresql.org
Backpatch-through: 14, where Memoize was added
src/backend/executor/nodeMemoize.c
src/backend/nodes/bitmapset.c
src/backend/optimizer/plan/createplan.c
src/backend/optimizer/util/clauses.c
src/include/nodes/execnodes.h
src/include/nodes/plannodes.h
src/include/optimizer/clauses.h
src/test/regress/expected/memoize.out
src/test/regress/sql/memoize.sql