Re: pg_upgrade and statistics

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: pg_upgrade and statistics
Дата
Msg-id CAM-w4HO4tmF16BApEotvFKViW4X0j=Et7sssZeKs+pnZwdU55w@mail.gmail.com
обсуждение исходный текст
Ответ на pg_upgrade and statistics  (Daniel Farina <daniel@heroku.com>)
Ответы Re: pg_upgrade and statistics
Re: pg_upgrade and statistics
Re: pg_upgrade and statistics
Список pgsql-hackers
On Tue, Mar 13, 2012 at 1:38 AM, Daniel Farina <daniel@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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: foreign key locks, 2nd attempt
Следующее
От: Robert Haas
Дата:
Сообщение: Re: patch for parallel pg_dump