From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: yarik97.6@gmail.com
Subject: BUG #16927: Postgres can`t access WAL files
Date: Mon, 15 Mar 2021 14:19:57 +0000
Message-ID: <16927-67c570d968c99567@postgresql.org> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, yarik97.6@gmail.com
Subject: Re: BUG #16927: Postgres can`t access WAL files
In-Reply-To: <16927-67c570d968c99567@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox