From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: no universally correct setting for fsync |
Date: | 2010-05-08 00:16:23 |
Message-ID: | D9EB8B28CCC10C46B7DD3472@amenophis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
--On 7. Mai 2010 19:49:15 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bernd Helmle <mailings(at)oopsware(dot)de> writes:
>> I've recently even started to wonder if the performance gain with
>> fsync=off is still that large on modern hardware. While testing large
>> migration procedures to a new version some time ago (on an admitedly
>> fast storage) i forgot here and then to turn it off, without a
>> significant degradation in performance.
>
> That says to me either that you're using a battery-backed write cache,
> or your fsyncs don't really work (no write barriers or something like
> that).
>
Well, yes, BBU present and proven storage. Maybe i'm wrong, but it seems
battery backed write caches aren't that seldom even in low end systems
nowadays.
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-05-08 00:17:53 | Re: [HACKERS] no universally correct setting for fsync |
Previous Message | Tom Lane | 2010-05-08 00:13:32 | Re: [HACKERS] no universally correct setting for fsync |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-05-08 00:17:53 | Re: [HACKERS] no universally correct setting for fsync |
Previous Message | Tom Lane | 2010-05-08 00:13:32 | Re: [HACKERS] no universally correct setting for fsync |