Re: [PATCH] Do not use StdRdOptions in Access Methods - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] Do not use StdRdOptions in Access Methods
Date
Msg-id 20191028150220.GA18542@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] Do not use StdRdOptions in Access Methods  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] Do not use StdRdOptions in Access Methods
Re: [PATCH] Do not use StdRdOptions in Access Methods
List pgsql-hackers
On 2019-Oct-23, Michael Paquier wrote:

> On Wed, Oct 23, 2019 at 11:16:25AM +0900, Amit Langote wrote:
> > IMO, parts of the patch that only refactors the existing code should
> > be first in the list as it is easier to review, especially if it adds
> > no new concepts.  In this case, your patch to break StdRdOptions into
> > more manageable chunks would be easier to understand if it built upon
> > a simplified framework of parsing reloptions text arrays.
> 
> Thanks for doing a split.  This helps in proving the point that this
> portion has independent value.

Not a split, yes?  AFAICS this code is nowhere in Nikolay's proposed
patchset -- it seems completely new development by Amit.  Am I wrong?

I also think that this has value -- let's go for it.  I think I'll be
back on Wednesday to review it, if you would prefer to wait.

Thanks

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Proposition to use '==' as synonym for 'IS NOT DISTINCT FROM'
Next
From: Shay Rojansky
Date:
Subject: strpos behavior change around empty substring in PG12