Manfred Spraul wrote:

Tom Lane wrote:

Seriously though, if we can move the bulk of the writing work into
background processes then I don't believe that there will be any
significant penalty for regular backends.  And I believe that it would
be a huge advantage from a correctness point of view if we could stop
depending on sync().

Which function guarantees that renames of WAL files arrived on the disk? AFAIK sync() is the only function that guarantees that.

What about the sync app from sysinternals? It seems Mark Russinovich figured out how to implement sync on Win32:

It requires administrative priveledges, but it shouldn't be that difficult to write a tiny service that runs in the LocalSystem account, listens to a pipe and syncs all disks when asked.

I think we'd have to do it from scratch, because of these license terms:


There is no charge to use any of the software published on this Web site at home or at work, so long as each user downloads and installs the product directly from

A commercial license is required to redistribute any of these utilities directly (whether by computer media, a file server, an email attachment, etc.) or to embed them in- or link them to- another program.

Also, do we want to force a broad brush sync() of just fsync our own files?



---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings

Reply via email to