From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ExecPrepareExprList and per-query context |
Date: | 2017-04-11 00:54:52 |
Message-ID: | d85afb62-96c8-3652-797a-4d8f682198a6@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2017/04/08 1:49, Tom Lane wrote:
> Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)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 :-().
Thanks for the fix.
>> 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.
I guess you're right. I was just thinking that passing a List through
ExecPrepareExpr() used to work and now it doesn't.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-04-11 00:55:01 | Re: SUBSCRIPTIONS and pg_upgrade |
Previous Message | Michael Paquier | 2017-04-11 00:53:45 | Re: Compiler warning in costsize.c |