Re: Windows now has fdatasync()

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Windows now has fdatasync()
Date: 2022-02-05 01:46:22
Message-ID: CA+hUKGLuyDYewWPGCq5M7Xv=RXxTW6PJ4eRVx=kj+XBN2j1uUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 5, 2022 at 12:54 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Feb 4, 2022 at 4:24 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > I'm not proposing we change our default to this new level, because it
> > doesn't work on non-NTFS, an annoying complication. This patch would
> > just provide something faster to put after "Alternatively".
>
> Hmm. I thought NTFS had kind of won the filesystem war on the Windows
> side of things. No?

Against FAT, yes, but there are also SMB/CIFS (network) and the new
ReFS (which we recently broke and then unbroke[1]). I haven't tried
those things, lacking general Windows-fu, but I suppose they'd reject
this and we'd panic, because the docs say "file systems supported:
NTFS"[2].

[1] https://www.postgresql.org/message-id/flat/16854-905604506e23d5c0%40postgresql.org
[2] https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-ntifs-ntflushbuffersfileex

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2022-02-05 03:20:49 Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations
Previous Message Ken Kato 2022-02-05 01:46:05 Re: [PATCH] Add min() and max() aggregate functions for xid8