Re: optimization ideas for frequent, large(ish) updates
От
Christopher Kings-Lynne
Тема
Re: optimization ideas for frequent, large(ish) updates
Дата
Msg-id
402EFADD.4040100@familyhealth.com.au
Ответ на
Re: optimization ideas for frequent, large(ish) updates (Marinos J. Yannikos)
Список
Дерево обсуждения
optimization ideas for frequent, large(ish) updates in frequently
accessed DB? "Marinos J. Yannikos" <mjy@geizhals.at>
Re: optimization ideas for frequent, large(ish) updates in frequently accessed DB? Josh Berkus <josh@agliodbs.com>
Re: optimization ideas for frequent, large(ish) updates "Marinos J. Yannikos" <mjy@geizhals.at>
Re: optimization ideas for frequent, large(ish) updates Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: optimization ideas for frequent, large(ish) updates Jeff Trout <jeff@jefftrout.com>
Re: optimization ideas for frequent, large(ish) updates "Marinos J. Yannikos" <mjy@geizhals.at>
Re: optimization ideas for frequent, large(ish) updates Tom Lane <tgl@sss.pgh.pa.us>
Re: optimization ideas for frequent, large(ish) updates in frequently accessed DB? Manfred Koizar <mkoi-pg@aon.at>
Re: optimization ideas for frequent, large(ish) updates in frequently accessed DB? Manfred Koizar <mkoi-pg@aon.at>
Re: optimization ideas for frequent, large(ish) updates in frequently accessed DB? Manfred Koizar <mkoi-pg@aon.at>
> 800MB is correct, yes... There are usually only 10-30 postgres processes > active (imagine 5-10 people working on the web front-end while cron > jobs access the db occasionally). Very few queries can use such large > amounts of memory for sorting, but they do exist. But remember that means that if you have 4 people doign 2 sorts each at the same time, postgres will use 6.4GB RAM maximum. The sort_mem parameter means that if a sort is larger than the max, it will be done in disk swap. Chris
В списке pgsql-performance по дате отправления
От: Marinos J. Yannikos
Дата: