mirror of
https://github.com/postgres/postgres.git
synced 2025-10-24 01:29:19 +03:00
Eliminate duplicative hashtempcxt in nodeSubplan.c.
Instead of building a separate memory context that's used just for running hash functions, make the hash functions run in the per-tuple context of the node's innerecontext. This saves a little space at runtime, and it avoids needing to reset two contexts instead of one inside buildSubPlanHash's main loop. This largely reverts commit133924e13. That's safe to do now becausebf6c614a2decoupled the evaluation context used by TupleHashTableMatch from that used for hash function evaluation, so that there's no longer a risk of resetting the innerecontext too soon. Per discussion of bug #19040, although this is not directly a fix for that. Author: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Haiyang Li <mohen.lhy@alibaba-inc.com> Reviewed-by: Fei Changhong <feichanghong@qq.com> Discussion: https://postgr.es/m/19040-c9b6073ef814f48c@postgresql.org
This commit is contained in:
@@ -1020,7 +1020,6 @@ typedef struct SubPlanState
|
||||
bool havehashrows; /* true if hashtable is not empty */
|
||||
bool havenullrows; /* true if hashnulls is not empty */
|
||||
MemoryContext hashtablecxt; /* memory context containing hash tables */
|
||||
MemoryContext hashtempcxt; /* temp memory context for hash tables */
|
||||
ExprContext *innerecontext; /* econtext for computing inner tuples */
|
||||
int numCols; /* number of columns being hashed */
|
||||
/* each of the remaining fields is an array of length numCols: */
|
||||
|
||||
Reference in New Issue
Block a user