Re: BUG #16927: Postgres can`t access WAL files
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Ярослав Пашинский <yarik97.6@gmail.com>
Cc: Postgres bugs <pgsql-bugs@lists.postgresql.org>
Date: 2021-03-16T08:40:17Z
Lists: pgsql-bugs
(Please keep pgsql-bugs in CC of this thread) On Tue, Mar 16, 2021 at 10:16:29AM +0200, Ярослав Пашинский wrote: > 2021-03-15 00:08:20.563 EET [9936] LOG: could not rename temporary > statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": > Permission denied This pattern is new. > I got this error also after updating from 9.6 to 13.2 Oh, sorry, I did not understand your last message as you used the word "updating", which sounded like you ran a set of minor updates for multiple servers and saw the same issue across all those versions. But what you mean is that you did one major upgrade, from 9.6 to 13. > So, the solution could be to rollback to 9.6 and then update to 12.X > version? There has been a collection of reports lately with 13.X misbehaving when it comes to the recycling of WAL segments: https://www.postgresql.org/message-id/3861ff1e-0923-7838-e826-094cc9bef737@hot.ee https://www.postgresql.org/message-id/16874-c3eecd319e36a2bf@postgresql.org https://www.postgresql.org/message-id/095ccf8d-7f58-d928-427c-b17ace23cae6@burgess.co.nz Your report is the 4th one of its kind, and based on the data collected up to now, 12.X or older major versions do not see the issue. I have begun a thread about the problem on -hackers, that's too much to be a coincidence, and more than one version of Windows sees the problem: https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW@paquier.xyz -- Michael
Commits
-
Fix concurrency issues with WAL segment recycling on Windows
- 78c24e97dd18 13.3 landed
- 909b449e00fc 14.0 landed