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 1ppkQY-0001pF-Hh for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Apr 2023 06:39:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ppkQX-0006r4-D7 for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Apr 2023 06:39:25 +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 1ppkQX-0006qr-2r for pgsql-hackers@lists.postgresql.org; Fri, 21 Apr 2023 06:39:25 +0000 Received: from mail-qv1-xf2e.google.com ([2607:f8b0:4864:20::f2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ppkQU-004BML-Ku for pgsql-hackers@postgresql.org; Fri, 21 Apr 2023 06:39:24 +0000 Received: by mail-qv1-xf2e.google.com with SMTP id 6a1803df08f44-5ed99ebe076so16063676d6.2 for ; Thu, 20 Apr 2023 23:39:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1682059161; x=1684651161; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UBO77gLcQLDAy5sIX2jr1o9Lg5eTt5o7fN5Rf8sy19k=; b=WIiMG826G1T92oqhIU5gH/Pfoylr9R0LASMMu8F0ppDK2TqzEEbxM486qLzIAHg11n NrNmdgN+6Ji7dQ0x8hSMcCnXUDp4ImMofzoaKITBBxqLGEhtxKn8i/h1c88duc3Mxi0k o4Ai2FgTGVTdxzX3GWoVCwd/nOle/fdqkCyCcQqNwf8nQ8X3bKzDQbRVbS4CnwLV3X6w J+r+u8F7VKQO441GaQRylXOM9kHmyQbx5XcsdqqHT2ehT1WMBExh0oM7SCl7vm6S5Tov wtOwpS98Fr7Ln8ldF8G01BlioyrZQw5BCvwSxwjfQKnRKc/YYKlYwlhAjmUnpxpiZrh3 LcWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682059161; x=1684651161; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UBO77gLcQLDAy5sIX2jr1o9Lg5eTt5o7fN5Rf8sy19k=; b=TGvg+eThjvkwKWlWWXjgxiAC7OJok6eTkMAqxLJFVNmfIuJLFA0jdv6fX1R0hbUhIQ BUPDvmoCnDNhER2jFTHwmblzFgfu+4pFVcLvt+ALUZttJAb5OvBQPWVXooGlqVfY4Y+b a2EJ1fuILVWmvEC8tg6ebjhLbPNrFotjC1PfkVDR+EkhovjPD0aMN0Oezrf9UxfDpHxD 2DCzlC8/Q3EQTHb5IlFxAXXbsK3MwfpCBkh2WJyDEKIU6MtZymEiPXycn4yWzZJSTF/M M3eorMdlshcM+i04EtM3Mp7MaeLiZNZSAJYbGzzpfgb32AT3cFeH6/1CHcz2wfSC7wJn GNTg== X-Gm-Message-State: AAQBX9f5hrX3jp1f7dc24ugoWGLRcS9sFmYaYGp1MlHjKL+90ZJr32Ue XaqJxrzUc04KICslDkskqGxGZqOQxJD6J0Ve4MgIkG3hiwtD76Fz5PmBXYTXpkG76pAWMW9x4ca cMjjhHrgV07bULBcXykjDarxRWvDmvRYtnA7Rk5+SGg9bNa7MkIqWQNRVsTrAn/dv3hIFu7UPut DaOfhwONpjzyYJCif51gYgTTxg3louQoEfuHU//6T3GtJvUDZsltCwizBYKIP2GHdTDw== X-Google-Smtp-Source: AKy350a2t6lYshRvR0gBavL1yLGpFST8IqY8t/Nx8dz2qnsL+soWIYbbVPC+HYqVJxRrXfmxKkBbq5sJh3KD3/78dH4= X-Received: by 2002:a05:6214:3018:b0:607:e40:c7c3 with SMTP id ke24-20020a056214301800b006070e40c7c3mr649948qvb.6.1682059160685; Thu, 20 Apr 2023 23:39:20 -0700 (PDT) MIME-Version: 1.0 From: Jakub Wartak Date: Fri, 21 Apr 2023 08:39:10 +0200 Message-ID: Subject: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns To: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi -hackers, I would like to ask if it wouldn't be good idea to copy the https://wiki.postgresql.org/wiki/TOAST#Total_table_size_limit discussion (out-of-line OID usage per TOAST-ed columns / potential limitation) to the official "Appendix K. PostgreSQL Limits" with also little bonus mentioning the "still searching for an unused OID in relation" notice. Although it is pretty obvious information for some and from commit 7fbcee1b2d5f1012c67942126881bd492e95077e and the discussion in [1], I wonder if the information shouldn't be a little more well known via the limitation (especially to steer people away from designing very wide non-partitioned tables). Regards, -J. [1] - https://www.postgresql.org/message-id/flat/16722-93043fb459a41073%40postgresql.org