On Tue, Aug 13, 2013 at 10:31 PM, Vlad Arkhipov <arhi...@dc.baikal.ru> wrote: > I used to use VACUUM FULL periodically to resolve the issue, but the problem > arises again in 2-3 months. > Here is the statistics (from pgstattuple). I run VACUUM FULL on 2013-08-07. > > date | relpages | reltuples | table_len | tuple_count | tuple_percent > | dead_tuple_count | dead_tuple_len | free_space | free_percent | > autovacuum_count > ------------+----------+-----------+-----------+-------------+---------------+------------------+----------------+------------+--------------+------------------ > 2013-08-08 | 39029 | 109096 | 319725568 | 37950 | 1.66 > | 52540 | 7355600 | 296440048 | 92.72 |
Are you sure you did "VACUUM FULL pg_attribute" on Aug 7, could you please confirm that free_percent arises from 0 to 92% in one day? Do you have some processes that intensively create tables or columns and then delete them or create them in transaction and rollback the transaction? -- Kind regards, Sergey Konoplev PostgreSQL Consultant and DBA http://www.linkedin.com/in/grayhemp +1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979 gray...@gmail.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
