Re: [PATCH] New [relation] option engine

Nikolay Shaplov <dhyan@nataraj.su>

From: Nikolay Shaplov <dhyan@nataraj.su>

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jeff Davis <pgsql@j-davis.com>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Michael Paquier <michael@paquier.xyz>, Amit Langote <amitlangote09@gmail.com>

Date: 2022-07-12T04:47:22Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Tighten test_predtest's input checks, and improve error messages.
- 00ac25a3c365 17.0 cited
Avoid reference to nonexistent array element in ExecInitAgg().
- 92957ed98c5c 16.0 cited
Clean up newlines following left parentheses
- c4f113e8fef9 15.0 cited

Attachments

new_options_take_two_v03b.patch (text/x-patch) patch

В письме от вторник, 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 
master.

-- 
Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM: @dhyan:nataraj.su