Re: ExecPrepareExprList and per-query context
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-04-07T16:49:17Z
Lists: pgsql-hackers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes: > Should ExecPrepareExprList also switch to estate->es_query_cxt? Good point; I'm surprised we haven't noted any failures from that. We surely want the entire result data structure to be in the same memory context. There are not very many callers right now, and I guess they are all in the right context already (or we aren't testing them :-(). > Or maybe > ExecPrepareExpr could itself detect that passed-in node is a List and > create the list of ExprState nodes by itself. -1. That's just breaking the API of ExecPrepareExpr. regards, tom lane
Commits
-
Ensure that ExecPrepareExprList's result is all in one memory context.
- dbb2a931478a 10.0 landed