BUG #16927: Postgres can`t access WAL files
The Post Office <noreply@postgresql.org>
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: yarik97.6@gmail.com
Date: 2021-03-15T14:19:57Z
Lists: pgsql-bugs
The following bug has been logged on the website: Bug reference: 16927 Logged by: Ярослав Пашинский Email address: yarik97.6@gmail.com PostgreSQL version: 13.2 Operating system: Windows Server 2019 Description: 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 Best regards, Yaroslav.
Commits
-
Fix concurrency issues with WAL segment recycling on Windows
- 78c24e97dd18 13.3 landed
- 909b449e00fc 14.0 landed