Re: More thoughts about planner's cost estimates
| От | Hannu Krosing |
|---|---|
| Тема | Re: More thoughts about planner's cost estimates |
| Дата | |
| Msg-id | 1149360367.3889.8.camel@localhost.localdomain обсуждение исходный текст |
| Ответ на | Re: More thoughts about planner's cost estimates (Jim Nasby <jnasby@pervasive.com>) |
| Ответы |
Re: More thoughts about planner's cost estimates
|
| Список | pgsql-hackers |
Ühel kenal päeval, L, 2006-06-03 kell 10:43, kirjutas Jim Nasby: > Might also be worth adding analyze delay settings, ala > vacuum_cost_delay. Actually we should have delay settings for all potential (almost-)full-scan service ops, - VACUUM, ANALYSE, CREATE INDEX, ADD CONSTRAINT, maybe more - so that there would be better chances of running those on busy databases without disastrous effects. Probably we should use the same settings for all these, not invent a new set for each. -- ---------------- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com
В списке pgsql-hackers по дате отправления: