Re: [ADMIN] Why does the WAL writer sit on completed segments (on Windows)? - Mailing list pgsql-admin

From Tom Lane
Subject Re: [ADMIN] Why does the WAL writer sit on completed segments (on Windows)?
Date
Msg-id 7418.1492448152@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Why does the WAL writer sit on completed segments (on Windows)?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [ADMIN] Why does the WAL writer sit on completed segments (onWindows)?  (Christian Ullrich <chris@chrullrich.net>)
List pgsql-admin
Magnus Hagander <magnus@hagander.net> writes:
> But all our files are opened with (FILE_SHARE_READ | FILE_SHARE_WRITE |
> FILE_SHARE_DELETE). So shouldn't this allow 7zip (or whatever) to open up
> the file, regardless of us holding it open? (Looking at
> https://msdn.microsoft.com/en-us/library/windows/desktop/aa363874(v=vs.85).aspx
> at least that's how I read it?)

My understanding of what Christian wrote is that 7zip is using flags
that specifically disallow "sharing".  The flags we use will allow other
programs to open the file(s) with default options, but a program that
is deliberately trying to be the sole user of the file can still notice
our opens.

            regards, tom lane


pgsql-admin by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [ADMIN] Why does the WAL writer sit on completed segments (on Windows)?
Next
From: Christian Ullrich
Date:
Subject: Re: [ADMIN] Why does the WAL writer sit on completed segments (onWindows)?