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-19T11:36:19Z
Lists: pgsql-bugs
On Fri, Mar 19, 2021 at 11:04:14AM +0200, Ярослав Пашинский wrote: > I didn't quite understand you here, is " aaaef7a " stands for patch name? There was a typo in one of my previous messages. What I was referring to is aaa3aedd. That's a commit of the Postgres code tree, if you are not familiar with git, here is a link to the code change: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=aaa3aedd >> " How much did you test the unpatched builds by the way? " > On cluster where load was caused by pgbench I met wal file access error > after about 1 hour, but on developer server with real load (usually up to > 100 connections) the error occurred after 2.5-3 hours. OK, thanks. My environments are not that sensitive to the issue, unfortunately. -- Michael
Commits
-
Fix concurrency issues with WAL segment recycling on Windows
- 78c24e97dd18 13.3 landed
- 909b449e00fc 14.0 landed