I am also seeing a drift in the n_live_tup value compared to actual row count
on the table on PG9.0.6
It drifts after a vacuum , you can bring it back closer to the actual number
by running ANALYSE several times, you can lock it back into the right value
with a vacuum full, but then if you run a vacuum it shows a n_live_tup less
than the actual rows in the table.
This is on a table seeing 80% HOT updates. Its a table that is heavily
updated.
Server not running autovacuum
Tim
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Statistics-mismatch-between-n-live-tup-and-actual-row-count-tp5059317p5735108.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.