diff options
author | David Rowley <drowley@postgresql.org> | 2021-11-24 23:29:56 +1300 |
---|---|---|
committer | David Rowley <drowley@postgresql.org> | 2021-11-24 23:29:56 +1300 |
commit | c2dc7b9e15039ce90c0a631ff291feb81d2c8051 (patch) | |
tree | 07729c689c4f0a51b2dccd4d679edee283c194a6 /src/include/nodes/plannodes.h | |
parent | 0e681fa458750b08a5c7885820320fb85cd9ddf1 (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/include/nodes/plannodes.h')
-rw-r--r-- | src/include/nodes/plannodes.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/include/nodes/plannodes.h b/src/include/nodes/plannodes.h index e29c1ad8180..5ddf9479715 100644 --- a/src/include/nodes/plannodes.h +++ b/src/include/nodes/plannodes.h @@ -801,6 +801,7 @@ typedef struct Memoize uint32 est_entries; /* The maximum number of entries that the * planner expects will fit in the cache, or 0 * if unknown */ + Bitmapset *keyparamids; /* paramids from param_exprs */ } Memoize; /* ---------------- |