Re: Use outerPlanState() consistently in executor code

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use outerPlanState() consistently in executor code
Date: 2015-05-04 20:23:30
Message-ID: CA+TgmobeNSCoBM93JTH3zSUHnbckXC2vH7fT0h0iAAH_N0S8hA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 1, 2015 at 1:05 PM, Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> wrote:
> On Thu, Apr 30, 2015 at 5:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> I think I'd have done many of these as
>>
>> + PlanState *outerPlan = outerPlanState(node);
>>
>> rather than finding assorted random places to initialize the variables.
>>
>
> Agreed. Attached patch is revision along this line. Except for a few
> that delayed assignments does not look a random kludge, I moved most
> of others together with the declaration.

I fixed several whitespace errors, reverted the permissions changes
you included, adjusted the remaining call site to be the way Tom wants
(and I think he's right), and committed this.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-05-04 20:48:10 Re: Providing catalog view to pg_hba.conf file - Patch submission
Previous Message Stephen Frost 2015-05-04 19:00:35 Re: Auditing extension for PostgreSQL (Take 2)