summaryrefslogtreecommitdiff
path: root/src/backend/nodes/outfuncs.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2021-11-24 23:29:56 +1300
committerDavid Rowley <drowley@postgresql.org>2021-11-24 23:29:56 +1300
commitc2dc7b9e15039ce90c0a631ff291feb81d2c8051 (patch)
tree07729c689c4f0a51b2dccd4d679edee283c194a6 /src/backend/nodes/outfuncs.c
parent0e681fa458750b08a5c7885820320fb85cd9ddf1 (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/outfuncs.c')
-rw-r--r--src/backend/nodes/outfuncs.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/nodes/outfuncs.c b/src/backend/nodes/outfuncs.c
index c8863288fc8..da212d9ddff 100644
--- a/src/backend/nodes/outfuncs.c
+++ b/src/backend/nodes/outfuncs.c
@@ -861,6 +861,7 @@ _outMemoize(StringInfo str, const Memoize *node)
WRITE_BOOL_FIELD(singlerow);
WRITE_BOOL_FIELD(binary_mode);
WRITE_UINT_FIELD(est_entries);
+ WRITE_BITMAPSET_FIELD(keyparamids);
}
static void