Re: [BUG] non archived WAL removed during production crash recovery
Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
pgsql-bugs@lists.postgresql.org, michael@paquier.xyz
Date: 2020-04-02T15:44:50Z
Lists: pgsql-bugs, pgsql-hackers
On Thu, 2 Apr 2020 23:55:46 +0900 Fujii Masao <masao.fujii@oss.nttdata.com> wrote: [...] > > Well, it seems to me that this is what you suggested few paragraph away: > > > > «.ready files are removed when either archive_mode!=always in standby > > mode» > > Yes, so I'm fine with that as the first consensus because the behavior > is obviously better than the current one. *If* the case where no WAL files > should be removed is found, I'd just like to propose the additional patch. Do you mean to want to produce the next patch yourself?
Commits
-
Fix interpolation in test name.
- e16e9204692c 11.10 landed
- af2d09fa1c28 12.5 landed
- 6fb1c5b52826 13.0 landed
- 47a3a1c3d498 14.0 landed
-
Add more TAP coverage for archive status with crash recovery of standbys
- ebf6de869276 13.0 landed
-
Fix handling of WAL segments ready to be archived during crash recovery
- 9eff11653962 9.5.22 landed
- c2d8ae0dfe84 9.6.18 landed
- 02657c42199c 10.13 landed
- 2d24ca00b750 11.8 landed
- 22db5269bfa1 12.3 landed
- 4e87c4836ab9 13.0 landed
-
Fix WAL recycling on standbys depending on archive_mode
- 78ea8b5daab9 12.0 cited