On Tue, Mar 13, 2012 at 05:46:06PM +0000, Greg Stark wrote:
> On Tue, Mar 13, 2012 at 1:38 AM, Daniel Farina <daniel(at)heroku(dot)com> wrote:
> > You probably are going to ask: "why not just run ANALYZE and be done
> > with it?"
> 
> Uhm yes. If analyze takes a long time then something is broken. It's
> only reading a sample which should be pretty much a fixed number of
> pages per table. It shouldn't take much longer on your large database
> than on your smaller databases.
> 
> Perhaps you're running vacuum analyze by mistake?

pg_upgrade recommends running this command:

	vacuumdb --all --analyze-only

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

• Re: pg_upgrade and statistics at 2012-03-13 17:46:06 from Greg Stark

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2012-03-13 18:53:26
	Subject: Re: pg_upgrade and statistics
Previous:	From: Peter Eisentraut	Date: 2012-03-13 18:32:14
	Subject: Re: patch: CREATE OR REPLACE FUNCTION autocomplete