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: Michael Paquier <michael@paquier.xyz>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
masao.fujii@oss.nttdata.com, pgsql-bugs@lists.postgresql.org
Date: 2020-04-22T16:17:17Z
Lists: pgsql-bugs, pgsql-hackers
Attachments
- 0001-v10-Fix-WAL-retention-during-production-crash-recovery.patch (text/x-patch) patch v10-0001
On Wed, 22 Apr 2020 17:58:24 +0200 Jehan-Guillaume de Rorthais <jgdr@dalibo.com> wrote: > On Wed, 22 Apr 2020 16:32:23 +0900 > Michael Paquier <michael@paquier.xyz> wrote: > > [...] > [...] > [...] > > This test seems useless to me. It should either be removed or patched to test > the signal has been removed after a second restartpoint. > > Please, find in attachment a patch for 9.6 implementing this. If it seems > reasonable to you, I can create the backpatch to 9.5. I found an extra useless line of code in v9 patch. Please, find in attachment v10. Sorry for this. Regards,
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