Skip site navigation (1) Skip section navigation (2)

Re: strange row number estimates in pg9.1rc1

From: "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: strange row number estimates in pg9.1rc1
Date: 2011-08-30 16:34:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, 30 Aug 2011, Tom Lane wrote:

> Sure enough, that's the problem.  pg_upgrade leaves relpages/reltuples
> set to zero, but it also imports the visibility map pages from the old
> cluster.  If the old visibility map shows the table as all-visible,
> then this happens when you try to VACUUM ANALYZE the table:
> 1. VACUUM doesn't process any pages, so it has no tuple density
> estimate.  It leaves reltuples set to zero, but it does set relpages.
> 2. ANALYZE scans some part of the table.  It gets a tuple density
> estimate for those pages ... but if that's only a small fraction of
> the table, it believes the zero estimate of tuple density elsewhere.
> So you get only a small update of reltuples.

Thanks for figuring this out.
I wonder what should be the best way to proceed for already migrated 
databases -- running analyze repeatedly may not be the best way for 
very large clusters with large tables...


Sergey E. Koposov, PhD
Institute for Astronomy, Cambridge/Sternberg Astronomical Institute
E-mail: math(at)sai(dot)msu(dot)ru

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2011-08-30 16:41:39
Subject: Re: strange row number estimates in pg9.1rc1
Previous:From: Andrew DunstanDate: 2011-08-30 16:23:58
Subject: Re: compile from git repository

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group