Re: Replacing lfirst() with lfirst_node() appropriately in planner.c

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Replacing lfirst() with lfirst_node() appropriately in planner.c
Date: 2017-07-14 08:55:11
Message-ID: CAFjFpRdpu5_c6YWhF2NfHyy2qYH9gsd_Yy_RkQ2LodsJ69_DgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 13, 2017 at 9:15 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Ashutosh Bapat wrote:
>
>> Happened to stumble across some instances of lfirst() which could use
>> lfirst_node() in planner.c. Here's patch which replaces calls to
>> lfirst() extracting node pointers by lfirst_node() in planner.c.
>
> Sounds good.
>
>> Are we carrying out such replacements in master or this will be
>> considered for v11?
>
> This is for pg11 definitely; please add to the open commitfest.

Thanks. Added. https://commitfest.postgresql.org/14/1195/
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-07-14 09:09:12 Re: Authentication mechanisms categorization
Previous Message Ashutosh Bapat 2017-07-14 08:54:21 Re: PgFDW connection invalidation by ALTER SERVER/ALTER USER MAPPING