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 1sPemM-005fOA-V6 for pgsql-general@arkaria.postgresql.org; Fri, 05 Jul 2024 08:58:54 +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 1sPemK-007t8i-Sv for pgsql-general@arkaria.postgresql.org; Fri, 05 Jul 2024 08:58:53 +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 1sPemK-007t8a-Ff for pgsql-general@lists.postgresql.org; Fri, 05 Jul 2024 08:58:53 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sPemI-000VOg-MY for pgsql-general@lists.postgresql.org; Fri, 05 Jul 2024 08:58:51 +0000 Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-52caebc6137so1270280e87.0 for ; Fri, 05 Jul 2024 01:58:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720169927; x=1720774727; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9GNd+V1ZPlmN/TsHckMDqEehTfRlAdrxkRdqRelG6KI=; b=iYMxFJNHw0iLM+6ZMPBlBPtYIfS3ZdZDxcGfZt9FtH2Hj22wjw50s71YGEbkyHhqwL 5Xz11Mse37syHVFSIa9HqQ7abBImW1o5mRXAXlyBYd50sBTM/Bzimn7c/ktYiB9XGh+z NCuFC/Hfwfc5rH8wd8jQKqPY5Rg/A5pASTy1hnrvsncQkqMl6DslFespPanSMwsBUNJi 2uzBF1XWXMVGuzfZ4Fr9+yJe2gGQdRg4uv/yM4vsmGDdMqWSaY3JhQ7wX5JJGT1LnMZi WZ8IDD7lCWoF6Ny85BFtDXxKucXF9kf5h1UT8u5mKpvYkJYPHtHn7ic1XwH6AJfzN31F PSvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720169927; x=1720774727; 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=9GNd+V1ZPlmN/TsHckMDqEehTfRlAdrxkRdqRelG6KI=; b=hGKIUV2wOtmyM6C1zpT55Z9/WcrdJViIUQ6pLkAZ5AKdkjviS0qsa41DDMHj7unPVd 2VBmp7TQwWly0CDyGrtigkpwu/KRyz9qHwnRVkqnA8nmGkZPKNoLaURf1rZjG1sKRdvm 9YrU0M0AGPrxrabaE5CjYNbDjIEA9LUe4nJtHLPFIR08eHYfa0lGrCJYn34teEts7vjp x2Y1vVGQWgPbMTHnEqPemr6kQfvqzblXn+R+bVObU/80SzvbhnU++p1LdlFDtZn0zwDW 2/a4uT9wfupyhxdLbU31kGJnHvqaeCX1sqNNQhbEQGJZivAdx4XhVQ4dn0VoWpQXeWPG TI4A== X-Forwarded-Encrypted: i=1; AJvYcCWYcxQg9/7p5jdSS7ASOpgNyFdySvjWet9wwQ/ch0b+JzEN7cXVc9FppigfVve4Gjd+7WbbltgQWVzYieMbrScS7rT01MFy2rZ3w3/KDYDAqfv2 X-Gm-Message-State: AOJu0Yz6dtezLixeOARY8REdJrG+7ET0EIzOOD7OGH2fwCZPSlurFyrz TcTkFWkB4Qx6zZYt7Ua79yfSzyiRwa7CIuhg6J63LX4A+vUDiyJo8PJ1Vg+emelqW+Z+yhJK975 CImPZ2bR+SO+DOYh5niBAOHY/ghI= X-Google-Smtp-Source: AGHT+IH0VnKXVD9DlJpUuECa17wBfF7iglF4O1J1WMP5GwDg3IV4h4XkJDDGXigCQHE7yOw2D8gRgyCUx6d4zMfw8jk= X-Received: by 2002:ac2:59de:0:b0:52e:9dee:a6f5 with SMTP id 2adb3069b0e04-52ea06c8cbemr2488591e87.46.1720169927368; Fri, 05 Jul 2024 01:58:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Rowley Date: Fri, 5 Jul 2024 20:58:35 +1200 Message-ID: Subject: Re: Design strategy for table with many attributes To: Lok P Cc: Guyren Howe , pgsql-general Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 5 Jul 2024 at 20:53, Lok P wrote: > However out of curiosity, if the roasted/compressed component or column which is JSON itself goes beyond 8k post compression, will it break then? No. The size limit of a varlena field such as TEXT, JSON or JSONB is 1GB. See "field size" in [1]. Please also read [2]. David [1] https://www.postgresql.org/docs/current/limits.html [2] https://www.postgresql.org/docs/current/storage-toast.html