| From: | Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no> |
|---|---|
| To: | Sean Chittenden <sean(at)chittenden(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: fsync or fdatasync |
| Date: | 2002-09-09 23:52:08 |
| Message-ID: | 20020910015207.U24188@vestdata.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Sep 09, 2002 at 04:43:04PM -0700, Sean Chittenden wrote:
> > We'll be glad to consider changing the default for a specific platform
> > if we have a reasonably convincing argument that the other value is
> > better. So far, not much study has been done of which method is best
> > on which platforms (and under what load conditions).
>
> heh, just a quick note: I had one of FreeBSD's kernel guru's point out
> that fsync() on linux is a no-op. I haven't had that src tree in
> years so I can't confirm, but I'm inclined to believe him. Just an
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.
--
Ragnar Kjørstad
Big Storage
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2002-09-10 00:11:27 | Re: fsync or fdatasync |
| Previous Message | Sean Chittenden | 2002-09-09 23:43:04 | Re: fsync or fdatasync |