| commit | 411137a429210e432f923264a8e313a9872910ca | |
| author | David Rowley <drowley@postgresql.org> | |
| Wed, 24 Nov 2021 10:29:14 +0000 (24 23:29 +1300) | ||
| committer | David Rowley <drowley@postgresql.org> | |
| Wed, 24 Nov 2021 10:29:14 +0000 (24 23:29 +1300) | ||
| tree | 2f635992ec138d1c68dbc38f77a6bcf3779a3fbd | treesnapshot (tar.gz zip) |
| parent | fb5961fd13b1262df280e400645bdf4ed192f058 | commitdiff |
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
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
12 files changed: