Re: [PATCH] New [relation] option engine

From: Nikolay Shaplov <dhyan(at)nataraj(dot)su>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: [PATCH] New [relation] option engine
Date: 2022-07-12 04:47:22
Message-ID: 1765175.6Pkayx49nB@thinkpad-pgpro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

В письме от вторник, 12 июля 2022 г. 07:30:40 MSK пользователь Nikolay Shaplov
> > What about table access methods? There have been a couple attempts to
> > allow custom reloptions for table AMs. Does this patch help that use
> > case?
> This patch does not add custom reloptions for table AM. It is already huge
> enough, with no extra functionality. But new option engine will make adding
> custom options for table AM more easy task, as main goal of this patch is to
> simplify adding options everywhere they needed. And yes, adding custom
> table AM options is one of my next goals, as soon as this patch is commit.

And here goes rebased version of the patch, that can be applied to current

Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM:

Attachment Content-Type Size
new_options_take_two_v03b.patch text/x-patch 196.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-07-12 05:01:18 Reducing the chunk header sizes on all memory context types
Previous Message Nikolay Shaplov 2022-07-12 04:30:40 Re: [PATCH] New [relation] option engine