mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-08 05:29:21 +02:00
5bba65de94
It is possible for VACUUM to scan no pages at all, if the visibility map
shows that all pages are all-visible. In this situation VACUUM has no new
information to report about the relation's tuple density, so it wasn't
changing pg_class.reltuples ... but it updated pg_class.relpages anyway.
That's wrong in general, since there is no evidence to justify changing the
density ratio reltuples/relpages, but it's particularly bad if the previous
state was relpages=reltuples=0, which means "unknown tuple density".
We just replaced "unknown" with "zero". ANALYZE would eventually recover
from this, but it could take a lot of repetitions of ANALYZE to do so if
the relation size is much larger than the maximum number of pages ANALYZE
will scan, because of the moving-average behavior introduced by commit
|
||
---|---|---|
.. | ||
attoptcache.c | ||
catcache.c | ||
inval.c | ||
lsyscache.c | ||
Makefile | ||
plancache.c | ||
relcache.c | ||
relmapper.c | ||
spccache.c | ||
syscache.c | ||
ts_cache.c | ||
typcache.c |