Csaba Nagy wrote: > Now when the queue tables get 1000 times dead space compared to their > normal size, I get performance problems. So tweaking vacuum cost delay > doesn't buy me anything, as not vacuum per se is the performance > problem, it's long run time for big tables is.
So for you it would certainly help a lot to be able to vacuum the first X pages of the big table, stop, release locks, create new transaction, continue with the next X pages, lather, rinse, repeat. This is perfectly doable, it only needs enough motivation from a knowledgeable person. -- 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
