Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1om0dK-0005MU-QU for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Oct 2022 22:36:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1om0dJ-00013b-JS for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Oct 2022 22:36:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1om0dJ-000136-7D for pgsql-hackers@lists.postgresql.org; Fri, 21 Oct 2022 22:36:53 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1om0dC-0000la-B0 for pgsql-hackers@postgresql.org; Fri, 21 Oct 2022 22:36:52 +0000 Received: by mail-ed1-x52a.google.com with SMTP id e18so11038020edj.3 for ; Fri, 21 Oct 2022 15:36:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sE5ARB74LeHMpRtRrFXXVXhOJCctXQvTNXNbgOPmd8E=; b=U0Q/s9geUGq26Sq8hcaYdocNY2/1DkCXW+iNCGUegfpRig1MGIPsXcYT0aWce1PjpO sw5jCLHaMLEK2ozIUjbuJYfl4NHQoy2XaZihQ8AfHj8YLw+/WQhW2ndUiQlsdM11CgD5 E0ATbKjWLIQRrUIrohl4V8O05h8cBsUDR4TvZj+ft0JlFvh0IaEYQkNTh1K5VPKKZL/j mDr1I/mCk2KiahORHV/Gv3XC0aPpW3CyfkK3iDWLNUavxXscC1R90EPM+F8oUNV3j/91 58zKGKZ+cHmnldi8ewYXgMnJ2ctAG7w1GR7IvKdK6qEH7TOwI33kijHNYl/OYrtvUdPw MkAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sE5ARB74LeHMpRtRrFXXVXhOJCctXQvTNXNbgOPmd8E=; b=7JUg1x200eQw17WGVBjnDiS4hfoppqX5lZTLXjzo4XnlBym1rmjqP4JKuulfGB8Knx qAfytyq8PcT0ZRGXndo9viXxbllQFkveaZ8OJSX3FupMNxHUFhf8youhZMSAzH2rCHfJ EecU1s6szdDrt1wh1TiDQqrS5YnJa0ws5Ha7g4B/aH2ivletSw4qsfdKuoMmj9oP8aYn 3ZexVimpiweP/2O7qgpIUFwGGhV3TlHBfYXb8RKfqw+c2BbYfKhXw2kvcpK6DYTPQYyW EcXLaupsKLFQL44i8rIbBjmo66BR+BlIHC5F0ur0mGiq1EziePm9YCNDl8jAgRRT9sxo hQPA== X-Gm-Message-State: ACrzQf1vJxZbwZFObehUS0Vcjeot1KIQ/gvRPKqpWiwj4dXEccvrusqh U7rpDpwv0RU3yDsX69A45GySZBNOQY8fU4dSuUY= X-Google-Smtp-Source: AMsMyM6FkNWnRFwoQoLSvbqz5baeO69XscrXpH+z5dA7TU5qLIcc2byKXTxfdbSnytxSvo5V9shzjJ9c+Hoc948WX6E= X-Received: by 2002:a17:906:db07:b0:77b:82cf:54af with SMTP id xj7-20020a170906db0700b0077b82cf54afmr18178051ejb.666.1666391805050; Fri, 21 Oct 2022 15:36:45 -0700 (PDT) MIME-Version: 1.0 References: <20220802153704.lhrqpqdrrlpandh7@awork3.anarazel.de> In-Reply-To: From: Nikita Malakhov Date: Sat, 22 Oct 2022 01:36:31 +0300 Message-ID: Subject: Re: Pluggable toaster To: Aleksander Alekseev Cc: pgsql-hackers , Jacob Champion , Andres Freund , Matthias van de Meent , Robert Haas , Greg Stark , Teodor Sigaev Content-Type: multipart/alternative; boundary="00000000000098c83905eb931398" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000098c83905eb931398 Content-Type: text/plain; charset="UTF-8" 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@timescale.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/ --00000000000098c83905eb931398 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi!

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

On Fri, Oct 21, 2022 at 4:01 PM Aleksande= r Alekseev <aleksander@times= cale.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-impleme= nted using TOAST API and is plugged in as Default Toaster;
> v23-0003-toaster-docs.patch - Pluggable TOAST API documentation packag= e

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=C2=A0
https://postgrespro.ru/
--00000000000098c83905eb931398--