Probably temp table related ...but catalog bloat on one of my databases appears to be pretty bad.
Is the below bloat (table and index) something to worry about?
pg_stat_all_tables show the relations ARE getting successfully vacuumed...
Any suggestions on eliminating? Not sure if tools like pg_reorg are appropriate (or effective) or even vacuum full (yikes).
I'd prefer not to take a complete outage - but I would if this bloat is really an issue.
(I know about "reindex system" (duh) - but as that requires me to take an outage, my question about IF the bloat is a cause for concern still stands....)
schemaname | tablename | tbloat | wastedbytes | iname | ibloat | wastedibytes
------------+--------------+--------+-------------+---------------------------------+--------+--------------
pg_catalog | pg_attribute | 9.0 | 27648000 | pg_attribute_relid_attnam_index | 243.5 | 361627648
pg_catalog | pg_attribute | 9.0 | 27648000 | pg_attribute_relid_attnum_index | 168.5 | 253894656
pg_catalog | pg_type | 10.8 | 4890624 | pg_type_oid_index | 135.8 | 28721152
pg_catalog | pg_type | 10.8 | 4890624 | pg_type_typname_nsp_index | 287.2 | 60956672
pg_catalog | pg_class | 10.3 | 4562944 | pg_class_oid_index | 94.1 | 26689536
pg_catalog | pg_class | 10.3 | 4562944 | pg_class_relname_nsp_index | 270.1 | 77144064
pg_catalog | pg_depend | 5.3 | 3948544 | pg_depend_reference_index | 337.0 | 156901376
pg_catalog | pg_depend | 5.3 | 3948544 | pg_depend_depender_index | 359.6 | 167436288
pg_catalog | pg_index | 6.1 | 1130496 | pg_index_indexrelid_index | 72.9 | 7659520
pg_catalog | pg_index | 6.1 | 1130496 | pg_index_indrelid_index | 72.9 | 7659520
(10 rows)
Thanks in advance
Is the below bloat (table and index) something to worry about?
pg_stat_all_tables show the relations ARE getting successfully vacuumed...
Any suggestions on eliminating? Not sure if tools like pg_reorg are appropriate (or effective) or even vacuum full (yikes).
I'd prefer not to take a complete outage - but I would if this bloat is really an issue.
(I know about "reindex system" (duh) - but as that requires me to take an outage, my question about IF the bloat is a cause for concern still stands....)
schemaname | tablename | tbloat | wastedbytes | iname | ibloat | wastedibytes
------------+--------------+--------+-------------+---------------------------------+--------+--------------
pg_catalog | pg_attribute | 9.0 | 27648000 | pg_attribute_relid_attnam_index | 243.5 | 361627648
pg_catalog | pg_attribute | 9.0 | 27648000 | pg_attribute_relid_attnum_index | 168.5 | 253894656
pg_catalog | pg_type | 10.8 | 4890624 | pg_type_oid_index | 135.8 | 28721152
pg_catalog | pg_type | 10.8 | 4890624 | pg_type_typname_nsp_index | 287.2 | 60956672
pg_catalog | pg_class | 10.3 | 4562944 | pg_class_oid_index | 94.1 | 26689536
pg_catalog | pg_class | 10.3 | 4562944 | pg_class_relname_nsp_index | 270.1 | 77144064
pg_catalog | pg_depend | 5.3 | 3948544 | pg_depend_reference_index | 337.0 | 156901376
pg_catalog | pg_depend | 5.3 | 3948544 | pg_depend_depender_index | 359.6 | 167436288
pg_catalog | pg_index | 6.1 | 1130496 | pg_index_indexrelid_index | 72.9 | 7659520
pg_catalog | pg_index | 6.1 | 1130496 | pg_index_indrelid_index | 72.9 | 7659520
(10 rows)
Thanks in advance
