MIME-Version: 1.0
References: <CAN-LCVMV3m+pzSDqOLyzgVRXA2zJ94n_T7kyAc2Z5JJpH018sA@mail.gmail.com>
 <20230206104917.sipa7nzue5lw2e6z@alvherre.pgsql> <CAN-LCVOv5is9dUn1U3KYy4hAhVK7tx6a7goOFmgbrGM7ZSAxRA@mail.gmail.com>
 <CAJ7c6TMZ7xySLzhygvzezPysyM5aZ6OjO8zHSUTO+GMBeL1a3g@mail.gmail.com>
 <CAEze2WhRJwr7MhkcckxpOAR5=6gUQQQmVdfPtvNu-u8J8RkzmA@mail.gmail.com>
 <CAJ7c6TOrdn8XxieKWFGCnGmEMDXeac_PArdP1Y6Zmio0jJHpkg@mail.gmail.com> <CALT9ZEEdU5nuyVu1MhB=nRXtSk4CxH7pE7GTv0uwskXwK-MtgA@mail.gmail.com>
In-Reply-To: <CALT9ZEEdU5nuyVu1MhB=nRXtSk4CxH7pE7GTv0uwskXwK-MtgA@mail.gmail.com>
From: Nikita Malakhov <hukutoc@gmail.com>
Date: Wed, 14 Jun 2023 13:05:24 +0300
Message-ID: <CAN-LCVOqaz1_RhBLR=QW=LyzzGLDfAt9T4Cg1LQpbMG9r8e9LA@mail.gmail.com>
Subject: Re: Pluggable toaster
To: Pavel Borisov <pashkin.elfe@gmail.com>
Cc: Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, 
	Alvaro Herrera <alvherre@alvh.no-ip.org>, 
	Matthias van de Meent <boekewurm+postgres@gmail.com>, vignesh C <vignesh21@gmail.com>, 
	Jacob Champion <jchampion@timescale.com>, Andres Freund <andres@anarazel.de>, 
	Robert Haas <robertmhaas@gmail.com>, Greg Stark <stark@mit.edu>, Teodor Sigaev <teodor@sigaev.ru>
Content-Type: multipart/alternative; boundary="000000000000d4cd0e05fe1417ff"
Archived-At: <https://www.postgresql.org/message-id/CAN-LCVOqaz1_RhBLR%3DQW%3DLyzzGLDfAt9T4Cg1LQpbMG9r8e9LA%40mail.gmail.com>
Precedence: bulk

--000000000000d4cd0e05fe1417ff
Content-Type: text/plain; charset="UTF-8"

Hi!

I have a question for the community - why was this patch silently put to a
"rejected" status?
Should there no be some kind of explanation?

During this discussion I got the impression that for some reason some
members of the community
do not want the TOAST functionality, which has such drawbacks that make it
really a curse for
in many ways very good DBMS, to be touched. We cannot get rid of it because
of backwards
compatibility, so the best way is to make it more adaptable and extensible
- this is what this thread
is about. We proposed our vision on how to extend the TOAST Postgres-way,
like Pluggable
Storage some time before.

There are some very complex subjects left in this topic that really need a
community' attention.
I've mentioned them above, but there was no feedback on them.

Pavel, we've already had an update implementation for TOAST. But it is a
part of a Pluggable
TOAST and it hardly would be here without it. I've started another thread
on extending the TOAST
pointer, maybe you would want to participate there [1].

We still would be grateful for feedback.

[1] Extending the TOAST Pointer
<https://www.postgresql.org/message-id/flat/CAJ7c6TNAYyeMYKVkiwOZChy7UpE_CkjpYOk73gcWTXMkLkEyzw%40mail.gmail.com#59aacdde27dd61277fe7c46c61c84b2c>

-- 
Regards,
Nikita Malakhov
Postgres Professional
https://postgrespro.ru/

--000000000000d4cd0e05fe1417ff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi!<div><br></div><div>I have a question =
for the community - why was this patch silently put to a &quot;rejected&quo=
t; status?</div><div>Should there no be some kind of explanation?=C2=A0</di=
v><div><br></div><div>During this discussion I got the impression that for =
some=C2=A0reason some members of the community</div><div>do not want the TO=
AST functionality, which has such drawbacks that make it really a curse for=
</div><div>in many ways very good DBMS, to be touched. We cannot get rid of=
 it because of backwards</div><div>compatibility, so the best way is to mak=
e it more adaptable and extensible - this is what this thread</div><div>is =
about. We proposed our vision on how to extend the TOAST Postgres-way, like=
 Pluggable</div><div>Storage some time before.</div><div><br></div><div>The=
re are=C2=A0some very complex subjects left in this topic that really need =
a community&#39; attention.</div><div>I&#39;ve mentioned them above, but th=
ere was no feedback on them.=C2=A0</div><div><br></div><div>Pavel, we&#39;v=
e already had an update implementation for TOAST. But it is a part of a Plu=
ggable</div><div>TOAST and it hardly would be here without it. I&#39;ve sta=
rted another thread on extending the TOAST</div><div>pointer, maybe you wou=
ld want to participate there [1].</div><div><br></div><div>We still would b=
e grateful for feedback.</div><div><br></div><div>[1]=C2=A0<a href=3D"https=
://www.postgresql.org/message-id/flat/CAJ7c6TNAYyeMYKVkiwOZChy7UpE_CkjpYOk7=
3gcWTXMkLkEyzw%40mail.gmail.com#59aacdde27dd61277fe7c46c61c84b2c">Extending=
 the TOAST Pointer</a><br></div><div><br></div></div>-- <br><div dir=3D"ltr=
" class=3D"gmail_signature"><div dir=3D"ltr"><div style=3D"color:rgb(34,34,=
34)">Regards,</div><div style=3D"color:rgb(34,34,34)">Nikita Malakhov<br></=
div><div style=3D"color:rgb(34,34,34)">Postgres Professional=C2=A0</div><di=
v style=3D"color:rgb(34,34,34)"><a href=3D"https://postgrespro.ru/" target=
=3D"_blank">https://postgrespro.ru/</a></div></div></div></div>

--000000000000d4cd0e05fe1417ff--