Re: [PATCH] New [relation] option engine

From: Nikolay Shaplov <dhyan(at)nataraj(dot)su>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 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-03-22 16:56:46
Message-ID: 4142565.V3TJ1GsxxI@thinkpad-pgpro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

В письме от вторник, 22 марта 2022 г. 03:46:10 MSK пользователь Andres Freund

> > I'd like to introduce a patch that reworks options processing.
> This doesn't apply anymore:
Thank you for sending this notice!

I've updated the patch to include new changes, that have been made in postgres

> 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:

Attachment Content-Type Size
new_options_take_two_v01a.diff text/x-patch 192.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-03-22 16:58:19 Re: New Object Access Type hooks
Previous Message Mark Dilger 2022-03-22 16:48:24 Re: New Object Access Type hooks