Re: Pluggable toaster

From: Nikita Malakhov <hukutoc(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Jacob Champion <jchampion(at)timescale(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: Pluggable toaster
Date: 2022-10-21 22:36:31
Message-ID: CAN-LCVN7V4RP6bwfXQriVShGhmod9NLj7K8esHx8YnovuJ1v4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

Aleksander, we have had this in mind while developing this feature, and
have checked it. Just a slight modification is needed
to make it work with Pluggable Storage (Access Methods) API.

On Fri, Oct 21, 2022 at 4:01 PM Aleksander Alekseev <
aleksander(at)timescale(dot)com> wrote:

> Hi Nikita,
>
> > Here's rebased patch:
> > v23-0001-toaster-interface.patch - Pluggable TOAST API interface with
> reference (original) TOAST mechanics - new API is introduced but
> > reference TOAST is still left unchanged;
> > v23-0002-toaster-default.patch - Default TOAST mechanics is
> re-implemented using TOAST API and is plugged in as Default Toaster;
> > v23-0003-toaster-docs.patch - Pluggable TOAST API documentation package
>
> Thanks for keeping the patch up to date.
>
> As I recall one of the open questions was: how this feature is
> supposed to work with table access methods? Could you please summarize
> what the current consensus is in this respect?
>
> --
> Best regards,
> Aleksander Alekseev
>

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-10-22 00:30:48 Re: Missing update of all_hasnulls in BRIN opclasses
Previous Message Thomas Munro 2022-10-21 21:24:06 Re: Collation version tracking for macOS