Alvaro Herrera wrote: > Pruning is going to take place on next vacuum anyway, isn't it? > > AFAIUI the point is that you can't do cleanup selectively only on UPDATE > because of pointers that your process may already have to the page, > which is why you wanted to do it on every heap_fetch. I suggest it is > optimization which can be left for a later version (8.4?)
Wait, did you mean that we don't do pruning at all in 8.3? That's a bad idea, the main purpose of HOT is to be able to vacuum page at a time, reducing the need to do regular vacuums. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
