diff options
| author | David Rowley <drowley@postgresql.org> | 2021-11-24 23:29:14 +1300 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-11-24 23:29:14 +1300 |
| commit | 411137a429210e432f923264a8e313a9872910ca (patch) | |
| tree | 2f635992ec138d1c68dbc38f77a6bcf3779a3fbd /src/backend/nodes/copyfuncs.c | |
| parent | fb5961fd13b1262df280e400645bdf4ed192f058 (diff) | |
Flush Memoize cache when non-key parameters change, take 2
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
Diffstat (limited to 'src/backend/nodes/copyfuncs.c')
| -rw-r--r-- | src/backend/nodes/copyfuncs.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/nodes/copyfuncs.c b/src/backend/nodes/copyfuncs.c index 7d55fd69ab3..297b6ee715f 100644 --- a/src/backend/nodes/copyfuncs.c +++ b/src/backend/nodes/copyfuncs.c @@ -973,6 +973,7 @@ _copyMemoize(const Memoize *from) COPY_SCALAR_FIELD(singlerow); COPY_SCALAR_FIELD(binary_mode); COPY_SCALAR_FIELD(est_entries); + COPY_BITMAPSET_FIELD(keyparamids); return newnode; } |