|From:||PG Bug reporting form <noreply(at)postgresql(dot)org>|
|Subject:||BUG #16927: Postgres can`t access WAL files|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
The following bug has been logged on the website:
Bug reference: 16927
Logged by: Ярослав Пашинский
Email address: yarik97(dot)6(at)gmail(dot)com
PostgreSQL version: 13.2
Operating system: Windows Server 2019
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  LOG: could not rename file
"pg_wal/000000010000086E000000C6": No such file or directory
2021-03-15 15:48:38.884 EET  LOG: could not rename file
"pg_wal/000000010000086D000000E7": Permission denied
2021-03-15 15:48:49.813 EET  LOG: could not rename file
"pg_wal/000000010000086D000000FD": Permission denied
2021-03-15 15:49:00.642 EET  LOG: could not rename file
"pg_wal/000000010000086E00000033": Permission denied
Best regards, Yaroslav.
|Next Message||Tom Lane||2021-03-15 16:06:16||Re: BUG #16926: initdb fails on Windows when binary path contains certain non-ASCII characters|
|Previous Message||David Steele||2021-03-15 12:18:29||Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch|