| From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Michael Kohl <michael(dot)kohl(at)tupalo(dot)com> |
| Subject: | Re: High load, |
| Date: | 2011-01-27 13:23:48 |
| Message-ID: | AANLkTi=ZoDQzy=M4JHfsPsU7sDYKHcVb8rvUTh3LiQXE@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2011/1/27 Andres Freund <andres(at)anarazel(dot)de>:
> On Thursday, January 27, 2011 12:24:10 PM Cédric Villemain wrote:
>> > maintenance_work_mem = 512MB
>> 128MB is usualy enough
> Uhm, I don't want to be picky, but thats not really my experience. Sorts for
> index creation are highly dependent on a high m_w_m. Quite regularly I find the
> existing 1GB limit a probleme here...
That is right for index creation, but not for 'pure' maintenance
stuff. Once the database is running as usual, there is no really point
to give auto-vacuum or auto-analyze much more (depend on the raid card
memory too ...)
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-01-27 13:26:38 | Re: High load, |
| Previous Message | Michael Kohl | 2011-01-27 12:56:35 | Re: High load, |