Re: Why does the WAL writer sit on completed segments (on Windows)?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Christian Ullrich <chris(at)chrullrich(dot)net>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Why does the WAL writer sit on completed segments (on Windows)?
Date: 2017-04-17 16:55:52
Message-ID: 7418.1492448152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Christian Ullrich 2017-04-17 17:07:33 Re: Why does the WAL writer sit on completed segments (on Windows)?
Previous Message Magnus Hagander 2017-04-17 16:38:39 Re: Why does the WAL writer sit on completed segments (on Windows)?