Re: BUG #16927: Postgres can`t access WAL files

On Mon, Mar 15, 2021 at 02:19:57PM +0000, PG Bug reporting form wrote:
> Recently, I had updated 4 clusters postgreSQL from version 9.6 to 13.2, and
> now have issue with errors that you can see below from log file. There is
> high frequency of how this error gets occurred.
> With such type of errors I can`t set up replication slot and I worry about
> is it safe for data in DB cluster.
> I already took some actions to get rid of this error: 1) enabled exclusions
> in GPO for Microsoft Defender (clusters directory and postgres process)
> 2) checked system with sfc tool.
> 3) checked user & system rights for cluster directory.
> But nothings from this works.
> Here are some lines from log file.
> 2021-03-15 15:44:54.674 EET [3992] LOG: could not rename file
> "pg_wal/000000010000086E000000C6": No such file or directory
> 2021-03-15 15:48:38.884 EET [3992] LOG: could not rename file
> "pg_wal/000000010000086D000000E7": Permission denied
> 2021-03-15 15:48:49.813 EET [3992] LOG: could not rename file
> "pg_wal/000000010000086D000000FD": Permission denied
> 2021-03-15 15:49:00.642 EET [3992] LOG: could not rename file
> "pg_wal/000000010000086E00000033": Permission denied

There have been multiple reports of this issue for 13, though we have
not been able to determine if this was coming from Postgres or if a
recent Windows update is causing that. Here, you basically say that
all stable versions of PostgreSQL are seeing this problem, which is
new to me. Particularly, 9.6.20 did not have any issues but 9.6.21
is showing this problem, right? Or did you update from an even older
version, say 9.6.19 or 9.6.18?

Are all those instances involved with streaming replication? What is
exactly the version of your Windows server? d726e44f catches my
eyes here, looking at the diffs between both versions..
--
Michael