Nolan Cafferky wrote: > The so far untried ideas I've had are: > > * Try out the autovacuum service > * Re-index tables (this hasn't been done for at least months, maybe never) > * Do some selective VACUUM FULL on high-use tables (materialized view > for report seems like a likely culprit, but also seems like it wouldn't > influence both databases) > * Restart postgres, restart the machine itself, and other useless handwaving
* Check whether there are open, idle transactions and close them -- 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
