Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
От | Greg Smith |
---|---|
Тема | Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter |
Дата | |
Msg-id | 4E8B8960.9030903@2ndQuadrant.com обсуждение исходный текст |
Ответ на | Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter (Venkat Balaji <venkat.balaji@verse.in>) |
Ответы |
Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter |
Список | pgsql-performance |
On 10/04/2011 03:50 AM, Venkat Balaji wrote: > I had a look at the pg_stat_bgwriter as well. Try saving it like this instead: select now(),* from pg_stat_bgwriter; And collect two data points, space a day or more apart. That gives a lot more information about the rate at which things are actually happening. The long-term totals are less interesting than that. Generally the first round of tuning work here is to increase checkpoint_segments until most checkpoints appear in checkpoints_timed rather than checkpoints_req. After that, increasing checkpoint_timeout might also be useful. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
В списке pgsql-performance по дате отправления: