Re: [PATCH] New [relation] option engine
Nikolay Shaplov <dhyan@nataraj.su>
From: Nikolay Shaplov <dhyan@nataraj.su>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
Michael Paquier <michael@paquier.xyz>, Amit Langote <amitlangote09@gmail.com>
Date: 2022-03-22T16:56:46Z
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_v01a.diff (text/x-patch) patch
В письме от вторник, 22 марта 2022 г. 03:46:10 MSK пользователь Andres Freund написал: > > I'd like to introduce a patch that reworks options processing. > This doesn't apply anymore: http://cfbot.cputube.org/patch_37_3536.log Thank you for sending this notice! I've updated the patch to include new changes, that have been made in postgres recently. > Given that this patch has been submitted just to the last CF and that > there's been no action on it, I don't see this going into 15. Yes it is not to be added in 15 for sure. > Therefore I'd like to move it to the next CF? The only reason it can be kept in current CF, is to keep it in front of the eyes of potential reviewers for one more week. So it is up to you, if you consider it does not worth it, you can move it now. No great harm would be done then. -- Nikolay Shaplov aka Nataraj Fuzzing Engineer at Postgres Professional Matrix IM: @dhyan:nataraj.su