On Tue, Mar 13, 2012 at 1:38 AM, Daniel Farina <dan...@heroku.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? If Analyze is taking a long time then we're getting the worst of both worlds. The statistics are very poor for certain metrics (namely ndistinct). The main reason we don't do better is because we don't want to do a full scan. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
