public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nikita Malakhov <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: vignesh C <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: pgsql-hackers <[email protected]>
Cc: Jacob Champion <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Matthias van de Meent <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Greg Stark <[email protected]>
Cc: Teodor Sigaev <[email protected]>
Subject: Re: Pluggable toaster
Date: Mon, 6 Feb 2023 16:38:01 +0300
Message-ID: <CAN-LCVOv5is9dUn1U3KYy4hAhVK7tx6a7goOFmgbrGM7ZSAxRA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAN-LCVMV3m+pzSDqOLyzgVRXA2zJ94n_T7kyAc2Z5JJpH018sA@mail.gmail.com>
<[email protected]>
Hi!
Existing TOAST has several very painful drawbacks - lack of UPDATE
operation, bloating of TOAST tables, and limits that are implicitly implied
on base tables by their TOAST tables, so it is seems not fair to say that
Pluggable TOAST does not solve any problems but just introduces new
ones.
The main reason behind this decision is that keeping the first
implementation
on the side of the vanilla (I mean rebasing it) over time is very difficult
due
to the very invasive nature of this solution.
So we decided to reduce changes in the core to the minimum necessary
to make it available through the hooks, because the hooks part is very
lightweight and simple to keep rebasing onto the vanilla core. We plan
to keep this extension free with the PostgreSQL license, so any PostgreSQL
user could benefit from the TOAST on steroids, and sometimes in the
future it will be a much simpler task to integrate the Pluggable TOAST into
the vanilla, along with our advanced TOAST implementations which
we plan to keep under Open Source licenses too.
On Mon, Feb 6, 2023 at 1:49 PM Alvaro Herrera <[email protected]>
wrote:
> On 2023-Feb-06, Nikita Malakhov wrote:
>
> > Currently we're busy revising the whole Pluggable TOAST API to make it
> > available as an extension and based on hooks to minimize changes in
> > the core. It will be available soon.
>
> Hmm, I'm not sure why would PGDG want to accept such a thing. I read
> "minimize changes" as "open source Postgres can keep their crap
> implementation and companies will offer good ones for a fee". I'd
> rather have something that can give users direct benefit -- not hide it
> behind proprietary licenses forcing each company to implement their own
> performant toaster.
>
> --
> Álvaro Herrera 48°01'N 7°57'E —
> https://www.EnterpriseDB.com/
>
--
Regards,
Nikita Malakhov
Postgres Professional
https://postgrespro.ru/
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Pluggable toaster
In-Reply-To: <CAN-LCVOv5is9dUn1U3KYy4hAhVK7tx6a7goOFmgbrGM7ZSAxRA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox