Re: [BUG] non archived WAL removed during production crash recovery

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>

Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, tgl@sss.pgh.pa.us, masao.fujii@oss.nttdata.com, pgsql-bugs@lists.postgresql.org

Date: 2020-04-28T00:41:06Z

Lists: pgsql-bugs, pgsql-hackers

On Tue, Apr 28, 2020 at 01:58:47AM +0200, Jehan-Guillaume de Rorthais wrote:
> Thank you guys for your help, reviews and commits!

The buildfarm does not complain after the latest commit, meaning that
we are good here.  Thanks for your efforts.
--
Michael

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