aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorRichard Guo <rguo@postgresql.org>2024-07-15 10:26:33 +0900
committerRichard Guo <rguo@postgresql.org>2024-07-15 10:26:33 +0900
commit069d0ff0226b9ac999030b894db8defd4df186e0 (patch)
tree3b5b4d64ed5e6a507d84806d3f96d662a6f5cebb /doc/src
parentf96c2c72788cab3005c8bc6b4934b4928b34a529 (diff)
downloadpostgresql-069d0ff0226b9ac999030b894db8defd4df186e0.tar.gz
postgresql-069d0ff0226b9ac999030b894db8defd4df186e0.zip
Check lateral references within PHVs for memoize cache keys
If we intend to generate a Memoize node on top of a path, we need cache keys of some sort. Currently we search for the cache keys in the parameterized clauses of the path as well as the lateral_vars of its parent. However, it turns out that this is not sufficient because there might be lateral references derived from PlaceHolderVars, which we fail to take into consideration. This oversight can cause us to miss opportunities to utilize the Memoize node. Moreover, in some plans, failing to recognize all the cache keys could result in performance regressions. This is because without identifying all the cache keys, we would need to purge the entire cache every time we get a new outer tuple during execution. This patch fixes this issue by extracting lateral Vars from within PlaceHolderVars and subsequently including them in the cache keys. In passing, this patch also includes a comment clarifying that Memoize nodes are currently not added on top of join relation paths. This explains why this patch only considers PlaceHolderVars that are due to be evaluated at baserels. Author: Richard Guo Reviewed-by: Tom Lane, David Rowley, Andrei Lepikhov Discussion: https://postgr.es/m/CAMbWs48jLxn0pAPZpJ50EThZ569Xrw+=4Ac3QvkpQvNszbeoNg@mail.gmail.com
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions