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>
 <CALT9ZEEhOMnvc6VqqHdP2vVnsTOR64DtOy6xFzsTyJ0VeZ72ZQ@mail.gmail.com>
 <CAJ7c6TNsOM6BW6uO9LxP5yjW9AbnWMX_Qae7nYE4Xw6F6mRtKA@mail.gmail.com> <CAN-LCVMniuPpBzCOW797e4JVc6TeWKjAA9P4KLe0Xu6dFHy7zw@mail.gmail.com>
In-Reply-To: <CAN-LCVMniuPpBzCOW797e4JVc6TeWKjAA9P4KLe0Xu6dFHy7zw@mail.gmail.com>
From: Aleksander Alekseev <aleksander@timescale.com>
Date: Fri, 16 Jun 2023 16:20:38 +0300
Message-ID: <CAJ7c6TOh9i62ciRNnGRDVnjJtmu8F4TeO4vevoxt6=LwSnrC3A@mail.gmail.com>
Subject: Re: Pluggable toaster
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Nikita Malakhov <hukutoc@gmail.com>, Pavel Borisov <pashkin.elfe@gmail.com>, 
	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/CAJ7c6TOh9i62ciRNnGRDVnjJtmu8F4TeO4vevoxt6%3DLwSnrC3A%40mail.gmail.com>
Precedence: bulk

Hi Nikita,

> We already have a lot of changes in Pluggable TOAST that were not committed
> to the main GIT branch of this thread, so it seems that I have to merge them and
> reopen it.

Pretty sure that reopening an already rejected patch that is competing
with compression dictionaries (which the rest of us are currently
focusing on) will achieve anything. Consider joining the compression
dictionaries effort instead [1]. During the discussion with the
community it ended up being a TOAST improvement after all. So we could
use your expertise in this area.

[1]: https://commitfest.postgresql.org/43/3626/

-- 
Best regards,
Aleksander Alekseev