| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade and statistics |
| Date: | 2012-03-13 18:52:29 |
| Message-ID: | 20120313185229.GA23967@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-03-13 18:53:26 | Re: pg_upgrade and statistics |
| Previous Message | Peter Eisentraut | 2012-03-13 18:32:14 | Re: patch: CREATE OR REPLACE FUNCTION autocomplete |