Re: ANALYZE and index/stats degradation
От
Gregory Stark
Тема
Re: ANALYZE and index/stats degradation
Дата
Msg-id
877ipj5a5c.fsf@oxford.xeocode.com
Ответ на
ANALYZE and index/stats degradation (Jeroen T. Vermeulen)
Список
Дерево обсуждения
ANALYZE and index/stats degradation "Jeroen T. Vermeulen" <jtv@xs4all.nl>
Re: ANALYZE and index/stats degradation Gregory Stark <stark@enterprisedb.com>
Re: ANALYZE and index/stats degradation "Jeroen T. Vermeulen" <jtv@xs4all.nl>
Re: ANALYZE and index/stats degradation Gregory Stark <stark@enterprisedb.com>
Re: ANALYZE and index/stats degradation "Jeroen T. Vermeulen" <jtv@xs4all.nl>
"Jeroen T. Vermeulen" writes: > So I suppose the planner has a good reason to ignore the index at that > point. I'm assuming that this is something to do with the correlation > between the index and the column's statistics degrading in some way. Best to post "explain analyze " for when the performance is good and bad. Perhaps also an explain analyze for the query with enable_seqscan off when it's bad. Also, which version of Postgres is this? It's possible you just need vacuum to run more frequently on this table and autovacuum isn't doing it often enough. In which case you might have a cron job run vacuum (or vacuum analyze) on this table more frequently. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления