Sriram Dandapani wrote: > Hi > I have several such databases to issue vacuum on. If I were to vacuum > each table individually, would the transaction id be updated after every > table vacuum.
No, you must issue database-wide vacuums. Single-table vacuums, even if done to each and every table, do not suffice. > Wonder if it is because I have several large partitioned tables that I > drop every day that don't get vacuumed enough. The best time of the day to do the vacuum would be just after one such partition was dropped, one would think. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
