Re: no universally correct setting for fsync

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
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-07 23:49:15
Message-ID: 3860.1273276155@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

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).

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Josh Berkus 2010-05-08 00:02:59 Re: [HACKERS] no universally correct setting for fsync
Previous Message Bernd Helmle 2010-05-07 23:32:59 Re: no universally correct setting for fsync

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2010-05-08 00:02:59 Re: [HACKERS] no universally correct setting for fsync
Previous Message Tom Lane 2010-05-07 23:46:42 Re: psql weird behaviour with charset encodings