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 1tuws5-00EoVz-Gi for pgsql-general@arkaria.postgresql.org; Wed, 19 Mar 2025 17:06:25 +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 1tuws3-00885K-Sn for pgsql-general@arkaria.postgresql.org; Wed, 19 Mar 2025 17:06:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tuws3-00885B-Ew for pgsql-general@lists.postgresql.org; Wed, 19 Mar 2025 17:06:23 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tuwrz-003nUc-2h for pgsql-general@lists.postgresql.org; Wed, 19 Mar 2025 17:06:23 +0000 Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-5e677f59438so11084102a12.2 for ; Wed, 19 Mar 2025 10:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742403980; x=1743008780; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=C4f6jvSIX7neYk9R04QA00RI0hiLCDj8rmMJKV2tJKk=; b=f7Schepbihtm5PUarfeQ4f86T7BZErQQ3WLvJAQKTCJlecg6ReKiqWFXjYNK2QhYxX PHPs5ayaDHMIBDJPC4TwAg1rwkce5GwGwkVofqUSFY3+Ld5odHy80WmRLE1MLBU6kvDa VuOw3/u9+/K5e1RQUZtFCNyrUuWeibcJ7cnb4EQokKQAlDYb87UvRJDxt963wXqgOJM4 6GCBzuEVBsFs0cF6yeLqGipJhDWiksca9i+hOWgabP0l/iQjNS0wxdINrFeH1EAWUbmL GEacTL05RVH2EoD0TAulLImgvPr9KuW7saDb1j3DcmGD5N5fmDGVoCi1TlJh/FFHA779 oyFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742403980; x=1743008780; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=C4f6jvSIX7neYk9R04QA00RI0hiLCDj8rmMJKV2tJKk=; b=g4+nrTNUsA/JeNcxASR09m0yvZ1YxDfsWy06wQLLF5xycYbs+vgXJeHT+buMH7s05k QFUG9jNZ7ynh0ytMcbqvZXORMfEF28dQb8Lkq0tyZdkpI4H4LCPDdQ6p8hta/2All/GN L3IFTsWHsziepka21xXD00ZDyhZ8+i62UP7Hs9dpu9Xnj+m0c8jvsGeCNUIXyYkU4hAz U4L5RWABAUb94WkdMZpr9GKnfPrmgTAzhzdIniIyZlHUdNp+tTSVTX++HAM3hCGCNsoE WD5NgK//fafROgd13E7i6iKePPPP6zH8SugCN5MdifBMHaPTrZhBuutJYxcBSxdS1vuj HtXg== X-Gm-Message-State: AOJu0YxhJDGeTARCV9B+ptjuaKSOG5WFxt7SPQZY4yPIXWP2PwvZ4Y7Q Fnw8quG08U7Qgz8sCaVbnKiUwQxRwX5+E5IA8V1QJKbKiXq4pP31TyAu3+7PkZB0v5+/skNkEyU 24FI1uFWEDZv67FWPmtTzv0HiNpWjU3aCuvk= X-Gm-Gg: ASbGncuDlfs5ICDKBVP/kq3EiSmbFmXfq6L2+Qre5zjrMWBZl1kiDq+jdvYF+56HoDQ d3zwqhxckMGhNq58la9RmM/qDZSNzHNbvvUCG7HZUyOcVud6cFbWpUTQU7cpR6diuanKwXP06L1 TehSH8xtfMKuYHMaYE4tjYl5pDIw== X-Google-Smtp-Source: AGHT+IG12EmDlcUoVyxX00tE08tFwwmbDP1P3NhSAvePYp2qVIufwIyKx6+Bg2Dt8ADCER+wkUA4Bq0V4uSjK8ncYcE= X-Received: by 2002:a05:6402:3487:b0:5e5:2c0a:448e with SMTP id 4fb4d7f45d1cf-5eb9f1d2a6cmr54882a12.6.1742403979681; Wed, 19 Mar 2025 10:06:19 -0700 (PDT) MIME-Version: 1.0 From: Siraj G Date: Wed, 19 Mar 2025 22:36:08 +0530 X-Gm-Features: AQ5f1JrRrYUhTY1euKXZcdzHE0AGQmmpyJ0xP1zRJ0y6jQveaQpfJqX56t3r0hQ Message-ID: Subject: size of attributes table is too big To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000043a7550630b50ad2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000043a7550630b50ad2 Content-Type: text/plain; charset="UTF-8" Hello! I have a PG (v16) instance which is occupying around 1TB of storage. Out of this, around 350GB is occupied by the table pg_catalog.pg_attribute. Why is the catalog table's size so big? Here are the sizes: pg_attribute 338 GB pg_attribute_relid_attnam_index 117 GB pg_attribute_relid_attnum_index 69 GB I think this table must have tons of dead tuples. Please suggest to me if we can purge any data/shrink the size of this table. REgards Siraj --00000000000043a7550630b50ad2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!

I have a PG (v16) instance which= is occupying around 1TB of storage. Out of this, around 350GB is occupied = by the table pg_catalog.pg_attribute.=C2=A0
Why is the catalog ta= ble's size so big?

Here are the sizes:

pg_attribute
338 GB
pg_attribute_relid_attnam_index
117 GB<= /div>
pg_attr= ibute_relid_attnum_index
69 GB

<= div>I think this table must have tons of dead tuples. Please suggest to me = if we can purge any data/shrink the size of this table.

REgards
Siraj
--00000000000043a7550630b50ad2--