Just to add a little more detail about my busy_table 1) there are no rows deleted 2) 98% of updates are HOT 3) there are two DB's on this postgres instance both with the same table, both seeing the same issue -- View this message in context: http://postgresql.1045698.n5.nabble.com/autovacuum-vacuum-creates-bad-statistics-for-planner-when-it-log-index-scans-0-tp5804416p5804424.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
