Re: size of attributes table is too big

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: size of attributes table is too big
Date: 2025-03-19 17:57:06
Message-ID: CANzqJaAxC71J3wQjvPv2N37X1cDfnD_x+F3+tcsjG69PorSMWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 19, 2025 at 1:06 PM Siraj G <tosiraj(dot)g(at)gmail(dot)com> wrote:

> 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.
>
>
Run pgstattuple and pgstatindex on them. They'll tell you how much bloat
you have.

And tune your autovacuum parameters to be more aggressive. These, for
example, are my settings:
autovacuum_analyze_scale_factor = 0.015
autovacuum_vacuum_scale_factor = 0.015
autovacuum_vacuum_insert_scale_factor = 0.015
autovacuum_vacuum_insert_threshold = 250

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Puspendu Panda 2025-03-19 18:07:29 Postgres incremental database updates thru CI/CD
Previous Message Adrian Klaver 2025-03-19 17:48:39 Re: size of attributes table is too big