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 1pOmI7-0007UY-8O for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Feb 2023 21:11:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pOmI5-0003it-Ca for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Feb 2023 21:11:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pOmI4-0003dt-TO for pgsql-hackers@lists.postgresql.org; Sun, 05 Feb 2023 21:11:13 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pOmHx-0005uB-SQ for pgsql-hackers@postgresql.org; Sun, 05 Feb 2023 21:11:11 +0000 Received: by mail-ej1-x62e.google.com with SMTP id m2so29068218ejb.8 for ; Sun, 05 Feb 2023 13:11:05 -0800 (PST) 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=1jgsxd9iYHM6tld214iCxHAw3BKFLhkxI4INLfAbxNo=; b=b7mURg8qhhmghi9uJR3a9MaW+mna5dK13AHAqTz2Zd3rlWszeT8XrL8rt4yVSrmfVY TxW91LpYtilwpLLx7/45aJCYXyVlDHLydguaWlNDcK6HW0MO7EG+C4oWpSr18id7ulyx B0iCPb/+AKZJpum91+CEWigLwiT5WnMfB3pPJ+WiFQ83YiaGVuX4JQ/aBZZ+GXwMNOpq va+VYmRvhcofCkHBCrEWQcOfwBZYA+yscwfnL13vqVhB2LOtRUAWuqN/He146z50zhl9 k20Orkm1qOQsaIegQzGN0hohSpq79N6F225wFoIM7bcbm9Ib3vbCZ4keghXVd095ROjK l8IA== 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=1jgsxd9iYHM6tld214iCxHAw3BKFLhkxI4INLfAbxNo=; b=sWGQWlB4xsUKFmk7+8q3Cyoc4LvwprV5m8kdL+YTI3TqX2ff+Zh/F2XtOu7/KGb3HI ekeEEU9D6Sf5nOaGK5+FwJDm4JnIim7qjmnJ623frR09xJxJio2HlymS3XG3whetU8kB OrBClID9l+itbpzbjyGk2BndRg2kwInqNcN/8twV806g8HImEaedbC8TrxB5Kr2DD6yh r1pDtYFE7YPW2VHOMaO5E6hHfb05krhaofBrCEq8zjh23iUIIh5Ac1pZBi9pkBlnayJf jEvEKjrqa2mS3IRV43mrVHxV6Jsd9fT2KSxd2W1mEnKzejM6g5QaWaz+NpZeSaztql3C 8t5A== X-Gm-Message-State: AO0yUKXBYaifQtIgOSRhZv7eOO2OnN2WYBsiu2XvSVRYyNY24c6i81An 7VGb8UtgsLPJ1Fmf6ZnhriBRvUpadN6qqQ6jCps= X-Google-Smtp-Source: AK7set+8wdURvXmLvncgsBqdP3fvrftr4HRQhBS5eFuL6Tgdj2rvczgUMR0UWFwNmUhpr+iykzmh1hJgrGaYJ/F5njI= X-Received: by 2002:a17:906:1858:b0:87b:dbb8:7918 with SMTP id w24-20020a170906185800b0087bdbb87918mr4976981eje.186.1675631464367; Sun, 05 Feb 2023 13:11:04 -0800 (PST) MIME-Version: 1.0 References: <20230203095658.imkcw2sypawe3py3@alvherre.pgsql> In-Reply-To: <20230203095658.imkcw2sypawe3py3@alvherre.pgsql> From: Nikita Malakhov Date: Mon, 6 Feb 2023 00:10:50 +0300 Message-ID: Subject: Re: Pluggable toaster To: Alvaro Herrera Cc: vignesh C , Aleksander Alekseev , pgsql-hackers , Jacob Champion , Andres Freund , Matthias van de Meent , Robert Haas , Greg Stark , Teodor Sigaev Content-Type: multipart/alternative; boundary="0000000000003549c005f3fa5a3e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003549c005f3fa5a3e Content-Type: text/plain; charset="UTF-8" Hi hackers! In response to opinion in thread on Compresson dictionaries for JSONb [1] >The approaches are completely different, >but they seem to be trying to fix the same problem: the fact that the >default TOAST stuff isn't good enough for JSONB. The problem, actually, is that the default TOAST is often not good for modern loads and amounts of data.Pluggable TOAST is based not only on pure enthusiasm, but on demands and tickets from production databases.The main demand is effective and transparent storage subsystem for large values for some problematic types of data, which we already have, with proven efficiency. So we're really quite surprised that it has got so little feedback. We've got some opinions on approach but there is no any general one on the approach itself except doubts about the TOAST mechanism needs revision at all. 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. > [1] https://postgr.es/m/20230203095540.zutul5vmsbmantbm@alvherre.pgsql > -- Nikita Malakhov Postgres Professional https://postgrespro.ru/ --0000000000003549c005f3fa5a3e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi hacke= rs!

In response to opinion= in thread on Compresson dictionaries for JSONb [1]
>The approaches are completely different,

>but they seem to be trying to fi= x the same problem: the fact that the
&g= t;default TOAST stuff isn't good enough for JSONB.





=

The problem, actua= lly, is that the default TOAST is often not good for




modern <= /font>loads and amounts of dat= a.Pluggable TOAST is ba= sed not only




= on pure enthusiasm, but on demands and tickets from production




databases.The main demand is effective an= d transparent storage subsystem




for large values for some problematic types of data, whi= ch we already have,




with proven effi= ciency.


<= br>


<= /span>



So we'r= e really quite surprised that it has got so little feedback. We've got<= /span>




=

some opinions= on approach but there is no any general one on the approach




itself except doubts abou= t the TOAST mechanism needs revision at all.







Currently we're busy = revising the whole Pluggable TOAST API to make it


<= p style=3D"box-sizing:border-box;margin-top:0px;color:rgb(0,0,0);white-spac= e:pre-wrap">


available as an exten= sion and based on hooks to minimize changes in




the core. It will be ava= ilable soon.


=C2= =A0
[1]=C2=A0=C2=A0ht= tps://postgr.es/m/20230203095540.zutul5vmsbmantbm@alvherre.pgsql
Nikita Malakhov
Postgres Professional=C2=A0
=
--0000000000003549c005f3fa5a3e--