On Thu, Aug 15, 2013 at 7:03 PM, Vlad Arkhipov <arhi...@dc.baikal.ru> wrote: >> Do you have some processes that intensively create tables or columns >> and then delete them or create them in transaction and rollback the >> transaction? >> > There are many processes that create and drop temporary tables.
That is the problem. Exactly what Jim was writing about. Autovacuum have no chance to clean dead tuples at the end of the table because they are created too intensively. In the latest versions autovacuum behaves so it would stop working when a concurrent lock is acquired. As he suggested you should use vacuum in cron, however it might make other procecess, that create/drop tables to wait. Another solution would be to factor out the temp tables usage from the logic. Could you please describe what are you using temp tables for? There might be another, more effective solution of this issue. -- 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 (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers