Greg, Tom, > But for most users analyze doesn't really have to run as often as > vacuum. One sequential scan per night doesn't seem like that big a deal > to me.
Clearly you don't have any 0.5 TB databases. > > I'd still be worried about the CPU pain though. ANALYZE can afford to > > expend a pretty fair number of cycles per sampled tuple, but with a > > whole-table sample that's going to add up. Agreed. Despite conventional wisdom, most PostgreSQL databases ... even those with high level OLTP or very large DW ... are CPU-bound. We really don't want an ANALYZE which is an order-of-magnitude increase in CPU activity. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
