Re: [HACKERS] Queuing all tables for analyze after recovery
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Queuing all tables for analyze after recovery |
Дата | |
Msg-id | 29877.1508446490@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | [HACKERS] Queuing all tables for analyze after recovery (Tomasz Ostrowski <tometzky+pg@ato.waw.pl>) |
Ответы |
Re: [HACKERS] Queuing all tables for analyze after recovery
Re: [HACKERS] Queuing all tables for analyze after recovery |
Список | pgsql-hackers |
Tomasz Ostrowski <tometzky+pg@ato.waw.pl> writes: > Some (maybe all) row statistics are lost after the database has > recovered after a failover. So it's recommended to ANALYZE all databases > in a cluster after recovery. Uh ... recommended by whom? pg_statistic has exactly the same reliability guarantees as the rest of the system catalogs. I don't deny that there might be cases where this is worth doing, but it does not seem so likely that it should be part of one's standard checklist. Much less something that we should expend a great deal of effort to automate. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: