Re: win32 performance - fsync question

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "E(dot)Rodichev" <er(at)sai(dot)msu(dot)su>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: win32 performance - fsync question
Date: 2005-02-17 15:21:48
Message-ID: 4214B68C.8000901@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

E.Rodichev wrote:

>
> This problem is addressed by file system (fsck, journalling etc.).
> Is it reasonable to handle it directly within application?
>
>

In the words of the Duke of Wellington, "If you believe that you'll
believe anything."

Please review past discussions on the mailing lists on this point.

BTW, most journalling file systems do not guarantee file integrity, only
file metadata integrity. In particular, I believe this is tru of NTFS
(and whether it even does that has been debated).

So by all means turn off fsync if you want the performance gain *and*
you accept the risk. But if you do, don't come crying later that your
data has been lost or corrupted.

(the results are interesting, though - with fsync off Windows and Linux
are in the same performance ballpark.)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-02-17 15:28:53 Re: Terminating a SETOF function call sequence
Previous Message Doug McNaught 2005-02-17 15:18:22 Re: win32 performance - fsync question