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> <CAN-LCVOqaz1_RhBLR=QW=LyzzGLDfAt9T4Cg1LQpbMG9r8e9LA@mail.gmail.com>
In-Reply-To: <CAN-LCVOqaz1_RhBLR=QW=LyzzGLDfAt9T4Cg1LQpbMG9r8e9LA@mail.gmail.com>
From: Pavel Borisov <pashkin.elfe@gmail.com>
Date: Wed, 14 Jun 2023 14:21:05 +0400
Message-ID: <CALT9ZEEhOMnvc6VqqHdP2vVnsTOR64DtOy6xFzsTyJ0VeZ72ZQ@mail.gmail.com>
Subject: Re: Pluggable toaster
To: Nikita Malakhov <hukutoc@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: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CALT9ZEEhOMnvc6VqqHdP2vVnsTOR64DtOy6xFzsTyJ0VeZ72ZQ%40mail.gmail.com>
Precedence: bulk

On Wed, 14 Jun 2023 at 14:05, Nikita Malakhov <hukutoc@gmail.com> wrote:
>
> 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
I don't see a clear reason it's rejected, besides technically it's
Waiting on Author since January. If it's a mistake and the patch is
up-to-date you can set an appropriate status.

Regards,
Pavel Borisov,
Supabase.