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 1q1cCB-0001ck-Ja for pgsql-hackers@arkaria.postgresql.org; Wed, 24 May 2023 00:17:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q1cC9-0000nB-0C for pgsql-hackers@arkaria.postgresql.org; Wed, 24 May 2023 00:17:37 +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 1q1cC7-0000n1-5z for pgsql-hackers@lists.postgresql.org; Wed, 24 May 2023 00:17:36 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q1cBz-001Xei-7s for pgsql-hackers@lists.postgresql.org; Wed, 24 May 2023 00:17:33 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F18675C0036; Tue, 23 May 2023 20:17:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 23 May 2023 20:17:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1684887445; x=1684973845; bh=lr vDMeG9kd35gDQg6zZxhL1OMGi4JRtoskDCG7wHOEo=; b=U+w8RwAWTe7MK8i8bF jqB4hh9hjoTuEa1gcUr3hl/qdbceU/Of4bjih8SCzKLYl057p8v+Sxz2CoillXNV Ga0lkRHnM81P2vua9sFzfY8P75Eu+96wqonA0QD0ID/aE8RTSnBRZp9hyvi42wEX TzqZXwVdcjv2dFH1k8BbdsBfaC+uFe63pn7osbie5bwXFeROatyzc3+BrU5JpxDe uZaRqsa7DXhJW20ys8Ibw48DZfgZP7JJGcokmWK9IeG7AA2IT1TjE0nNtWA4qhYR ClDIZnaLOwmuYkxgeFR9LLzwvgpTDch68j8Nu/NZUMBR/VvlwHSq6gLEkOxRHOJa m/Iw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1684887445; x=1684973845; bh=lrvDMeG9kd35g DQg6zZxhL1OMGi4JRtoskDCG7wHOEo=; b=rCMT4mI/RoXgFnu8E3gRH/eyh5/+I Fc/znjPv0CQIyQJ9fivfDuiYETzhVo1o9ZVU56StLpLBT5RInGYzO1en+rfb2Z54 0AJ1kj5n3ZMGVBgjkxvs/4rOolOhEQ3nx1ktyBbyY7q+eXkQpKV5uUlBiRwM3G4q v5zR8TkbqR8FG+0OcD3prRz8MadKnur4AYvG6f8jpSh2g4y9nM0btmzTAxZGOxYI Y9czGYPXixEeFBAaKdo0xIFOCoRUzvXz/dNaYG6Md6koVokByjdhgwcNnGMSlTJ5 bK883XGGtjPlMH4hxNTIxqxDzgflfnhWy8MeD1BjFUoTdhPx4YAygM9QQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeejgedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 23 May 2023 20:17:22 -0400 (EDT) Date: Wed, 24 May 2023 09:17:16 +0900 From: Michael Paquier To: Robert Haas Cc: Matthias van de Meent , Aleksander Alekseev , PostgreSQL Hackers , Nikita Malakhov Subject: Re: RFI: Extending the TOAST Pointer Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="t242MtS2ZdCz9uLF" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --t242MtS2ZdCz9uLF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, May 23, 2023 at 12:33:50PM -0400, Robert Haas wrote: > For projects like this, the details matter a lot. If the goal is to > add a new compression type that behaves like the existing compression > types, more or less, then I think we should allocate the last > ToastCompressionId bit to mean "some other compression ID" and add a > 1-byte header that says which one is in use. But if the new feature > being added is enough different from the other compression methods, > then it might be better to do it in some other way e.g. a new VARTAG. Agreed. While the compression argument and the possibility to add more options to toast pointers are very appealing, FWIW, I'd like to think that the primary target is the 4-byte OID assignment limit of where backends loop infinitely until a OID can be found, which can be a real pain for users with a large number of blobs or just enough toast data to trigger it. Saying that even if I sent the patch for zstd on toast.. -- Michael --t242MtS2ZdCz9uLF Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmRtV4wACgkQnvQgOdby QH3kDw/9FHs0vb22h0/Ntze4EwqpTOEL7X7KGKe6ROFjezp3WTp0JTpiBxji6Qch rPb0s2vSjGNHXVJkYnFBtvmY362tGfJ4qgrV8kb0n9W3TSGMWKjJMNPfR35pCBzK 7CgunddWVxdCktPHhllJIVo2jEWHfPSaaDkBHkWvpRmwnV6T8QDXULZ/7QV0NGe5 SmyCKzYwblFPIDBGZM/OKCIt5wSt01KJcP4QCyBLNITA4Awvg/VszgY4Y3bZToaG 4FY59HJ9vM5Cn3dy+D/dpr09yrnZC0MAlQCRg5xhBUX7ZXAYZh3n1lKVdGADEV1z 9xHNUJLdNrfnDTXkY6EX5gVZ1QoNil3WsdO/O8huNRBzcp9t6WV0slId7apS7FC/ 2dpP8qzppxjDaSa6zCeBdqjlmPdUGNwdWOIgTr+0jK/F3BUEjzUF6rkFG/+FgXd5 67T2i5JD2Kq+gbOHRWBI8brbFYyuAIZyPusMjXVR8OBf5joPRmJjtdyyC2hrZ4ng CHx5ex/wdtoNNFQMIp/JnLdn9eUIjnN5ayrKfWUVEZwNzQIrbxvrbXZqfHGoO940 DruFvFDMhwE2B1PYEYuEWursEx3rjF1apA9/6iBGkI9WucKyg4bualm6A8McO+hB pXKNfNm20/yH0JCDjVkAFjoG5bbvi/UZHBGl4yVFtDWGh8QTWlk= =f59g -----END PGP SIGNATURE----- --t242MtS2ZdCz9uLF--