pgsql: Add more TAP coverage for archive status with crash recovery of

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Add more TAP coverage for archive status with crash recovery of
Date: 2020-04-27 22:58:53
Message-ID: E1jTCiD-0000si-QU@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

This part of the test was included originally in 4e87c48, but got
reverted as of f9c1b8d because of timing issues in the test, where,
after more analysis, we found that the standbys may not have recovered
from the archives all the segments needed by the test. This stabilizes
the test by making sure that standbys replay up to the position returned
by pg_switch_wal(), meaning that all segments are recovered before the
manual checkpoint that tests WAL segment recycling and its interactions
with archive status files.

Author: Jehan-Guillaume de Rorthais
Reviewed-by: Kyotaro Horiguchi, Michael Paquier
Discussion: https://postgr.es/m/20200424034248.GL33034@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ebf6de8692766177a36e7f5fb7545a52a0d5d881

Modified Files
--------------
src/test/recovery/t/020_archive_status.pl | 38 +++++++++++++++++++++++++++++--
1 file changed, 36 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2020-04-28 08:30:49 pgsql: Fix definition of pg_statio_all_tables view
Previous Message Robert Haas 2020-04-27 18:07:20 pgsql: Fix bogus tar-file padding logic for standby.signal.