Re: Hard to maintain duplication in contain_volatile_functions_not_nextval_walker - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hard to maintain duplication in contain_volatile_functions_not_nextval_walker
Date
Msg-id CA+TgmobNUfob7hybx_r4Oion-vFTj8ipvZgHiRMgGyazduezzw@mail.gmail.com
Whole thread Raw
In response to Re: Hard to maintain duplication in contain_volatile_functions_not_nextval_walker  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Fri, May 27, 2016 at 10:36 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Sat, May 28, 2016 at 12:28 AM, Andres Freund <andres@anarazel.de> wrote:
>> contain_volatile_functions_walker is duplicated, near entirely, in
>> contain_volatile_functions_not_nextval_walker.
>
> Previously, I also had same observation.
>
>> Wouldn't it have been better not to duplicate, and keep a flag about
>> ignoring nextval in the context variable?
>
> makes sense.  +1 for doing it in the way as you are suggesting.

+1 from me, too.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Rename max_parallel_degree?
Next
From: Tom Lane
Date:
Subject: Re: Rename max_parallel_degree?