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

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

  1. Fix interpolation in test name.

  2. Add more TAP coverage for archive status with crash recovery of standbys

  3. Fix handling of WAL segments ready to be archived during crash recovery

  4. Fix WAL recycling on standbys depending on archive_mode