| From: | Craig James <craig_james(at)emolecules(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David Rees <drees76(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Occasional giant spikes in CPU load |
| Date: | 2010-04-08 02:06:15 |
| Message-ID: | 4BBD3A17.90209@emolecules.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 4/7/10 5:47 PM, Robert Haas wrote:
> On Wed, Apr 7, 2010 at 6:56 PM, David Rees<drees76(at)gmail(dot)com> wrote:
>>> max_fsm_pages = 16000000
>>> max_fsm_relations = 625000
>>> synchronous_commit = off
>>
>> You are playing with fire here. You should never turn this off unless
>> you do not care if your data becomes irrecoverably corrupted.
>
> That is not correct. Turning off synchronous_commit is sensible if
> you don't mind losing the last few transactions on a crash. What will
> corrupt your database is if you turn off fsync.
A bit off the original topic, but ...
I set it this way because I was advised that with a battery-backed RAID controller, this was a safe setting. Is that not the case?
Craig
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rees | 2010-04-08 02:50:35 | Re: Occasional giant spikes in CPU load |
| Previous Message | Robert Haas | 2010-04-08 00:47:18 | Re: Occasional giant spikes in CPU load |