| From: | ocie(at)paracel(dot)com |
|---|---|
| To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
| Cc: | mimo(at)interdata(dot)com(dot)pl, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] fsync -> fdatasync in backend/storage/file/fd.c |
| Date: | 1998-04-17 02:27:21 |
| Message-ID: | 9804170227.AA27585@dolomite.paracel.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> On Fri, 17 Apr 1998, Michal Mosiewicz wrote:
>
> > I don't remember if it has been mentioned.
> >
> > Anyhow, I think that it would be nice to change fsync'es into
> > fdatasync'es (of course as an autoconf-igurable option). I don't think
> > it's necessary to update all file's metadata each time a file is
> > flushed.
> >
> > I dunno where it's implemented. But it's for sure implemented in Linux.
>
> We don't have it (FreeBSD)...what does it do? *raised eyebrow*
> And, how many ppl actually have fsync's enabled?
It's a POSIX thing. fsync will sync the data and the metadata, but
fdatasync only syncs the data. So in the case of a crash, the inode
might not have the right date, etc. This can speed things up, but I
wouldn't venture a guess as to how much.
Ocie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-04-17 02:45:03 | Re: [INTERFACES] Re: ODBC driver |
| Previous Message | The Hermit Hacker | 1998-04-17 02:24:08 | Re: [HACKERS] fsync -> fdatasync in backend/storage/file/fd.c |