From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | shridhar(at)frodo(dot)hserus(dot)net |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint |
Date: | 2004-02-05 16:22:00 |
Message-ID: | 3593.1075998120@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> writes:
> There are other benefits of writing pages earlier even though they might not
> get synced immediately.
Such as?
> It would tell kernel that this is latest copy of updated buffer. Kernel VFS
> should make that copy visible to every other backend as well. The buffer
> manager will fetch the updated copy from VFS cache next time. All without
> going to disk actually..(Within the 30 seconds window of course..)
This seems quite irrelevant given the way we handle shared buffers.
> frequent fsyncs or frequent fsyncs per file descriptor written? I thought it
> was later.
You can only fsync one FD at a time (too bad ... if there were a
multi-file-fsync API it'd solve the overspecified-write-ordering issue).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-02-05 16:34:02 | Re: dollar quoting |
Previous Message | Tom Lane | 2004-02-05 16:14:00 | Re: dollar quoting |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-02-06 15:07:58 | Re: [HACKERS] Sync vs. fsync during checkpoint |
Previous Message | Magnus Hagander | 2004-02-05 15:34:36 | Re: win32 signals, part 4 |