Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qmMFC-006qXb-SQ for pgsql-docs@arkaria.postgresql.org; Fri, 29 Sep 2023 22:45:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qmMFB-006qns-5t for pgsql-docs@arkaria.postgresql.org; Fri, 29 Sep 2023 22:45:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qmMFA-006qnC-TN for pgsql-docs@lists.postgresql.org; Fri, 29 Sep 2023 22:45:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qmMF8-007Lu5-EJ for pgsql-docs@lists.postgresql.org; Fri, 29 Sep 2023 22:45:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 38TMjqx51421366; Fri, 29 Sep 2023 18:45:52 -0400 From: Tom Lane To: Laurenz Albe cc: Bruce Momjian , suchithjn22@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: The documentation for storage type 'plain' actually allows single byte header In-reply-to: <4977c12e127250fe9777ae57f6f5884b8f5c84ae.camel@cybertec.at> References: <167336599095.2667301.15497893107226841625@wrigleys.postgresql.org> <4977c12e127250fe9777ae57f6f5884b8f5c84ae.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Sat, 30 Sep 2023 00:35:00 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1421364.1696027552.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 29 Sep 2023 18:45:52 -0400 Message-ID: <1421365.1696027552@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > On Fri, 2023-09-29 at 18:19 -0400, Bruce Momjian wrote: >> Where did we end with this? Is a doc patch the solution? > I don't think this went anywhere, and a doc patch is not the solution. > Tom has argued convincingly that single-byte headers are an effect of th= e TOAST > system, and that STORAGE PLAIN should disable all effects of TOAST. Well, that was the original idea: you could use STORAGE PLAIN if you had C code that wasn't yet toast-aware. However, given the lack of complaints, it seems there's no non-toast-aware code left anywhere. And that's not too surprising, because the evolutionary pressure to fix such code would be mighty strong, and a lot of time has passed. I'm now inclined to think that changing the docs is better than changing the code; we'd be more likely to create new problems than fix anything useful. I wonder though if there's really just one place claiming that that's how it works. A trawl through the code comments might be advisable. regards, tom lane