Re: [PATCH] New [relation] option engine - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] New [relation] option engine
Date
Msg-id 202312081259.2pwkb25emowf@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] New [relation] option engine  (Nikolay Shaplov <dhyan@nataraj.su>)
Responses Re: [PATCH] New [relation] option engine
List pgsql-hackers
On 2023-Dec-08, Nikolay Shaplov wrote:

> Theoretically I can create patch with full options.c as it is in the patch 
> now, and use that code only in index AM, and keep reloption.c mostly 
> unchanged.
> 
> This will be total mess with two different options mechanisms working in the 
> same time, but this might be much more easy to review.  When we are done with 
> the first step, we can change the rest.
> If this will help to finally include patch into postgres, I can do it. Will 
> that help you to review?

I don't think that's better, because we could create slight
inconsistencies between the code used for index AMs and the users of
reloptions.

I'm not seeing any reasonable way to split this patch in smaller ones.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"No necesitamos banderas
 No reconocemos fronteras"                  (Jorge González)



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: GUC names in messages
Next
From: Daniel Gustafsson
Date:
Subject: Re: initdb caching during tests