On Wed, Mar 19, 2025 at 1:06 PM Siraj G <tosiraj.g@gmail.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_attribute338 GBpg_attribute_relid_attnam_index117 GBpg_attribute_relid_attnum_index69 GBI 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.015autovacuum_vacuum_scale_factor = 0.015autovacuum_vacuum_insert_scale_factor = 0.015autovacuum_vacuum_insert_threshold = 250-- Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.<Redacted> lobster!
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_attribute338 GBpg_attribute_relid_attnam_index117 GBpg_attribute_relid_attnum_index69 GBI 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.
pgsql-general by date:
Соглашаюсь с условиями обработки персональных данных