Bill Moran wrote: > The entire database was around 28M prior to the upgrades, etc. Immediately > after the upgrades, it was ~270M. Following a vacuum full, it dropped to > 165M. Following a database-wide reindex, it dropped to 30M.
Oh, so it was clearly the upgrade procedure that caused the bloat ... Reindexing seems the expected course. -- 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
