pgsql: Remove some unstable parts from new TAP test for archive status

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Remove some unstable parts from new TAP test for archive status
Date: 2020-04-24 02:35:13
Message-ID: E1jRoBN-000385-Hv@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Remove some unstable parts from new TAP test for archive status check

The test is proving to have timing issues when looking at archive status
files on standbys after crash recovery, while other parts of the test
rely on pg_stat_archiver as a wait point to make sure that a given state
of the archiving is reached. The coverage is not heavily impacted by
the removal those extra tests.

Per reports from several buildfarm animals, like crake, piculet,
culicidae and francolin.

Discussion: https://postgr.es/m/20200424005929.GK33034@paquier.xyz
Backpatch-through: 9.5

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/0d04e9d76aca0be5440d172ba5492389a6f6beb8

Modified Files
--------------
src/test/recovery/t/020_archive_status.pl | 17 +----------------
1 file changed, 1 insertion(+), 16 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-04-24 07:29:41 Re: pgsql: Skip WAL for new relfilenodes, under wal_level=minimal.
Previous Message Michael Paquier 2020-04-24 01:14:37 Re: pgsql: Fix handling of WAL segments ready to be archived during crash r