Thread: VACUUM ANALYZE AND ANALYZE ISSUE
Hi, I was running vacuum analyze on one of heavily bloated table. After the vacuum analyze completed . I did explain on a query . It was going for hash join and sequential scan. Then i issues ANALYZE BLOATED_TABLE; Then when ran explain query , surprisingly it was going for index scan . This was observed in postgres 9.0.1. Ideally VACUUM ANALYSE must have done VACCUM + ANALYZE. But ANALYZE part was pending. Which was completed when i ran analyze on that table . Can any one explain this? Did i miss anything. Rgrds Suhas -- View this message in context: http://postgresql.1045698.n5.nabble.com/VACUUM-ANALYZE-AND-ANALYZE-ISSUE-tp5749963.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
suhas.basavaraj12 <suhas.b@verse.in> wrote: > This was observed in postgres 9.0.1. You might want to review the bug fixes in 9.0 maintenance releases and see if any of them could be responsible for what you saw: http://www.postgresql.org/docs/9.0/static/release-9-0-2.html http://www.postgresql.org/docs/9.0/static/release-9-0-3.html http://www.postgresql.org/docs/9.0/static/release-9-0-4.html http://www.postgresql.org/docs/9.0/static/release-9-0-5.html http://www.postgresql.org/docs/9.0/static/release-9-0-6.html http://www.postgresql.org/docs/9.0/static/release-9-0-7.html http://www.postgresql.org/docs/9.0/static/release-9-0-8.html http://www.postgresql.org/docs/9.0/static/release-9-0-9.html http://www.postgresql.org/docs/9.0/static/release-9-0-10.html http://www.postgresql.org/docs/9.0/static/release-9-0-11.html http://www.postgresql.org/docs/9.0/static/release-9-0-12.html ... or just apply all of those bug fixes and see if you can make it happen again. In general, it pays to apply fixes as they become available. http://www.postgresql.org/support/versioning/ -- Kevin Grittner EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company