Re: Allow table AMs to define their own reloptions - Mailing list pgsql-hackers

From Yura Sokolov
Subject Re: Allow table AMs to define their own reloptions
Date
Msg-id a3697813-d5cf-40c4-b5a1-91a7605db570@postgrespro.ru
Whole thread Raw
In response to Re: Allow table AMs to define their own reloptions  (Julien Tachoires <julien@tachoires.me>)
List pgsql-hackers
04.03.2025 09:16, Julien Tachoires пишет:
> Hi Yura,
> 
> On Sun, Mar 02, 2025 at 06:20:07PM +0300, Yura Sokolov wrote:
>> Your forgot another one attempt discussion with patch [1] with alive
>> commitfest entry [2]
>>
>> [1] https://postgr.es/m/flat/3766675.7eaCOWfIcx%40thinkpad-pgpro
>> [2] https://commitfest.postgresql.org/patch/4688/
> 
> Thank you. After taking a look at the patch itself and the email thread,
> it seems this patch does not add custom reloptions to table AMs, see
> [1].
> 
> [1]: https://www.postgresql.org/message-id/1823308.yXV3o4JbTB%40thinkpad-pgpro

But intention of this patch is to make adding options easier, as author says:

  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.

I believe, adding generic way to options extension is better way than
targeting specific options. Don't you?

I believe Nikolay's patch needs review and support. As you're interesting
to the problem, may you at least look at his suggestion and analyze it from
the point of view of your task?

-------
regards
Yura Sokolov aka funny-falcon



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: encode/decode support for base64url
Next
From: Peter Eisentraut
Date:
Subject: Re: Next commitfest app release is planned for March 18th