| From: | Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no> |
|---|---|
| To: | Sean Chittenden <sean(at)chittenden(dot)org> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: fsync or fdatasync |
| Date: | 2002-09-10 00:28:20 |
| Message-ID: | 20020910022820.W24188@vestdata.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Sep 09, 2002 at 05:11:27PM -0700, Sean Chittenden wrote:
> > No, fsync() is not a no-op on linux.
> > Unless the filesystem is mounted with o_sync, I suppose - then
> > everything is written at write() so fsync() is not needed. But
> > generally, it does sync.
>
> Hrm, alright. From what I've figured out, about ~6wk ago fsync() was
> added to linux to have it actually fsync()... mind you someone quickly
> turned around and created a new patchset that ripped the functionality
> out and added it to an extreme linux distro. ::shrug:: <opinion>Linux
> is out of control.</opinion> -sc
"6wk"?
Linux has had fsync for as long as I can remember.
Maybe you have it confused with fsync() over NFS? The NFSv2
implementation on linux used to have "async" flag for nfs as default -
making it non NFS-compliant without reconfiguration.
--
Ragnar Kjørstad
Big Storage
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2002-09-10 00:33:18 | Re: fsync or fdatasync |
| Previous Message | Sean Chittenden | 2002-09-10 00:11:27 | Re: fsync or fdatasync |