Skip site navigation (1) Skip section navigation (2)

Re: fsync with sync, and Win32 unlink

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>
Cc: "PostgreSQL Win32 port list" <pgsql-hackers-win32(at)postgreSQL(dot)org>
Subject: Re: fsync with sync, and Win32 unlink
Date: 2004-03-11 09:04:38
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B447@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
> I have talked to Tom today and he is willing to implement the 
> discussed method of doing fsync on every file modified 
> between checkpoints, and add unlink handling for open files for Win32.

Great news. I'm sure this will benefig Unix platforms as well, when
taking into account the discussions previously.

<snip>

> 3)  On checkpoint request, either by the user or postmaster, 
> the background writer will create a subprocess, do a sync(), 
> wait, then do fsync of all files that were marked as dirty.  
> The sync() should flush out most of the dirty files in an 
> optimal manner.

Please make a config variable to make this sync() call optional. This
goes for Unix as well, and not just win32 (which doesn't support it).
Consider either a box with many different postgresql instances, or one
that run both postgresql and other software. Issuing sync() in that
sitaution will cause sync of a lot of data that probably doesn't need
syncing. 
But it'd probably be a very good thing on a dedicated server, giving the
kernel the chance to optimise.


//Magnus

pgsql-hackers by date

Next:From: Zeugswetter Andreas SB SDDate: 2004-03-11 09:38:40
Subject: Re: [HACKERS] fsync with sync, and Win32 unlink
Previous:From: Ramanujam H S IyengarDate: 2004-03-11 07:35:29
Subject: Re: How to get RelationName ??

pgsql-hackers-win32 by date

Next:From: Zeugswetter Andreas SB SDDate: 2004-03-11 09:38:40
Subject: Re: [HACKERS] fsync with sync, and Win32 unlink
Previous:From: Bruce MomjianDate: 2004-03-11 04:06:59
Subject: Timezone support

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group