From: Nikolay Shaplov <dhyan@nataraj.su>
To: jian he <jian.universality@gmail.com>, pgsql-hackers@lists.postgresql.org
Cc: Peter Smith <smithpb2250@gmail.com>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>,
 Yura Sokolov <y.sokolov@postgrespro.ru>, pgsql-hackers@lists.postgresql.org,
 Michael Paquier <michael@paquier.xyz>, Nikolay Shaplov <dhyan@nataraj.su>
Subject: Re: [PATCH] New [relation] option engine
Date: Thu, 06 Mar 2025 19:12:54 +0300
Message-ID: <2141678.KlZ2vcFHjT@thinkpad-pgpro>
Organization: Postgres Professional
In-Reply-To: <39561561.10thIPus4b@thinkpad-pgpro>
References: 
 <202312081259.2pwkb25emowf@alvherre.pgsql>
 <2220883.Mh6RI2rZIc@thinkpad-pgpro> <39561561.10thIPus4b@thinkpad-pgpro>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2152242.bB369e8A3T";
 micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: 
 <https://www.postgresql.org/message-id/2141678.KlZ2vcFHjT%40thinkpad-pgpro>
Precedence: bulk

--nextPart2152242.bB369e8A3T
Content-Type: multipart/mixed; boundary="nextPart2693827.k3LOHGUjKi";
 protected-headers="v1"
Content-Transfer-Encoding: 7Bit
From: Nikolay Shaplov <dhyan@nataraj.su>
Subject: Re: [PATCH] New [relation] option engine
Date: Thu, 06 Mar 2025 19:12:54 +0300
Message-ID: <2141678.KlZ2vcFHjT@thinkpad-pgpro>
Organization: Postgres Professional
In-Reply-To: <39561561.10thIPus4b@thinkpad-pgpro>
MIME-Version: 1.0

This is a multi-part message in MIME format.

--nextPart2693827.k3LOHGUjKi
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

=D0=92 =D0=BF=D0=B8=D1=81=D1=8C=D0=BC=D0=B5 =D0=BE=D1=82 =D1=81=D1=80=D0=B5=
=D0=B4=D0=B0, 26 =D1=84=D0=B5=D0=B2=D1=80=D0=B0=D0=BB=D1=8F 2025 =D0=B3. 22=
:33:58 MSK =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=
=BB=D1=8C Nikolay=20
Shaplov =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:

And new rebase. Conflict with 8492feb9 commit needed manual resolving.

And since I am writing anyway, will say couple of words about the patch.

Some colleagues of mine says, that they would be happy to have ability to a=
dd=20
custom namespaces to heap options. They write extensions that adds this or=
=20
that feature to the storage, and this feature might need some custom=20
configuring. And it would be nice to configure it via heap-options. We alre=
ady=20
have namespaces in reloptions, we can have more and make them custom.

This patch does not provide custom namespaces to reloptions, but it replace=
s=20
current reloption engine with a new one. And this new engine is very flexib=
le,=20
you can easily add custom namespaces using it.=20

So review this patch now, and you will have custom  option namespaces in=20
future (I think I will write it too)  :-)

=2D-=20
Nikolay Shaplov aka Nataraj
=46uzzing Engineer at Postgres Professional
Matrix IM: @dhyan:nataraj.su

--nextPart2693827.k3LOHGUjKi
Content-Disposition: attachment; filename="v-12-0001-New-options-engine.patch"
Content-Transfer-Encoding: 7Bit
Content-Type: text/x-patch; charset="unicode-2-0-utf-8";
 name="v-12-0001-New-options-engine.patch"