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 1pPLNd-00059R-2T for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Feb 2023 10:39:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPLNb-0001rv-NG for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Feb 2023 10:39:15 +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 1pPLNb-0001rb-E2 for pgsql-hackers@lists.postgresql.org; Tue, 07 Feb 2023 10:39:15 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pPLNZ-00084a-LF for pgsql-hackers@postgresql.org; Tue, 07 Feb 2023 10:39:15 +0000 Received: by mail-ej1-x62d.google.com with SMTP id sa10so11597042ejc.9 for ; Tue, 07 Feb 2023 02:39:13 -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=xWjmBTF7T5b04p/fcloM3Np4nGOVZK1zrdgMg4/xpbY=; b=dMPVIPs9qGZHucy7GSERpAKqbQj+ggaS78oyVpUy2doY/F3pAlU1MvDah1AL+wX0G9 9g2cswWcOvoOdr3DKZdCFPzDzGYasBKTVSO7nxf72n6lS4/0bvOicGkeYPyFUIqEjOZh HpXAOPplDNzUpGeBiXPT9c/IJNouyJWE7CQOWbXf0Zm7ddMZZEZNhvCZRSjrHi5L9LHb fEYGVg2rLTjf+u0fdqFznFTTd8HBUxG/flB8A74yofAK/6sHICV9DeuUussBO6PYvbjW 3J+CUxNXTey/3EDh56SdXhDL5QZ+v9wjsWgrXW8GeWZe+di8FQOxeAiIeqA2z0XLF2Kn BI9w== 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=xWjmBTF7T5b04p/fcloM3Np4nGOVZK1zrdgMg4/xpbY=; b=zfAGU07LAyzSJ4SEVa0IdHEhyrBaxX7XhicW1xFVbu/9bHYoYJg15zhJV/29UzmUBR g+6H+GvPfWs+0n4HMECFW1PrSBm5K3lVA2Q3FSEZFtvmGLBRR9zT11VnCiDee4sz5RrC 5wxApr7SU2bu7ML8jQC1hmjusnYTQJiX4g9jUh2Zipsc+5aAZMikqfHRokIwP1Wd1Owi KXoGFewNEwIITY0zBcnAWRoffWRPv2EcUjev/+0nWYOQgZubgRqFf6pijfsw3+OVnC5f fZUrnegtzXMq988zjcIDHsl5/Aa7pbkNHduBaux6YLojRl1klxG9DbdSlqLSI7peljYU uLVQ== X-Gm-Message-State: AO0yUKVGvjyFGtAk5ujKo/fIA/QhDF29OrL4r2Rlnmsw848zuo1/yBlv K4K2HZLU1EKNLkoM5P4LTcO5C7jLZWSyNuJxi/M= X-Google-Smtp-Source: AK7set/eU8RXid7hnR1iP4JCkpacVcoaGxyHtWKb7H8RlQsPm+U4NDauVIV3X3YxdbW56914VaaeHB/VE5Zkrsa51RE= X-Received: by 2002:a17:906:2757:b0:8a6:536b:c3e8 with SMTP id a23-20020a170906275700b008a6536bc3e8mr739973ejd.39.1675766352764; Tue, 07 Feb 2023 02:39:12 -0800 (PST) MIME-Version: 1.0 References: <20230206104917.sipa7nzue5lw2e6z@alvherre.pgsql> In-Reply-To: From: Pavel Borisov Date: Tue, 7 Feb 2023 14:38:20 +0400 Message-ID: Subject: Re: Pluggable toaster To: Aleksander Alekseev Cc: pgsql-hackers , Alvaro Herrera , Matthias van de Meent , Nikita Malakhov , vignesh C , Jacob Champion , Andres Freund , Robert Haas , Greg Stark , Teodor Sigaev Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, hackers! Maybe I've read the thread too superficially, but for me, it seems like more of a discussion on what TOAST should NOT be. Maybe someone more in the topic could explain what is the consensus on what we require and what we like to to have in a new TOAST? For me, a good toast should be chunk-updatable, so that we don't need to rewrite the whole TOAST and WAL-replicate the whole thing at every small attribute modification. But obviously, it's just another opinion. Kind regards, Pavel Borisov