Re: more anti-postgresql FUD

From: AgentM <agentm(at)themactionfaction(dot)com>
To: pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: more anti-postgresql FUD
Date: 2006-10-13 19:10:52
Message-ID: 093E468E-CE71-4E26-B258-BCB6516230DE@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


On Oct 13, 2006, at 14:36 , Joshua D. Drake wrote:

> Stephen Frost wrote:
>> * Alexander Staubo (alex(at)purefiction(dot)net) wrote:
>>> What formula did you use to get to that number? Is there a generic
>>> way on Linux to turn off (controller-based?) write caching?
>>
>> Just a side-note, but if you've got a pretty good expectation that
>> you
>> won't be without power for 24 consecutive hours ever you can get a
>> controller with a battery-backed write cache (some will do better
>> than
>> 24 hours too). For the performance concerned... :)
>
> No to mention if you are *that* concerned you could buy a generator
> for
> 500 bucks that will keep the machine alive if you absolutely have to.
>
> There is nothing wrong with write back cache as long as you have the
> infrastructure to support it.

Why does the battery have to be at that level? It's seems like a
reasonable poor man's solution would be to have a standard $50 UPS
plugged in and have the UPS signal postgresql to shut down and sync.
Then, theoretically, it would be safe to run with fsync=off. The
level of risk seems the same no?

-M

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2006-10-13 19:18:58 Re: more anti-postgresql FUD
Previous Message J S B 2006-10-13 19:03:17 Re: Backup DB not getting connected

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2006-10-13 19:18:58 Re: more anti-postgresql FUD
Previous Message Jim C. Nasby 2006-10-13 19:10:45 Re: [PATCHES] index advisor