"Sergey E. Koposov" <math(at)sai(dot)msu(dot)ru> writes:
> I'm seeing something weird which looks like a bug in 9.1rc1 after the
> upgrade 8.4->9.0->9.1 done using pg_upgrade.
Hm, I wonder what pg_upgrade left relpages/reltuples set to ...
> INFO: "lassource": found 0 removable, 0 nonremovable row versions in 0
> out of 6451184 pages
VACUUM is deciding that the table is all-visible and it need not scan
any of it ...
> INFO: "lassource": scanned 30000 of 6451184 pages, containing 270000 live
> rows and 0 dead rows; 30000 rows in sample, 806239 estimated total rows
... and then ANALYZE is scanning only 30000 of 6451184 pages, so even
though it knows the correct tuple density in those pages, it's not
licensed to change the reltuples total very much. If reltuples is way
off base to start with, then it will take a lot of ANALYZE cycles to
converge on a saner value. However, this doesn't leave us much closer
to understanding why it's off base to start with.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Ding Yuan||Date: 2011-08-30 07:15:19|
|Subject: BUG #6184: Inconsistencies in log messages|
|Previous:||From: Tom Lane||Date: 2011-08-30 04:59:01|
|Subject: Re: spinlocks on HP-UX |