From 06afd1cdaaf1cc9b0dd6c6b3b6fd1e1fa9618810 Mon Sep 17 00:00:00 2001 From: Kalen Krempely Date: Mon, 22 Apr 2019 11:04:35 -0700 Subject: [PATCH] gprecoverseg: add multi-host tablespace test Skip gprecoverseg tablespace tests until tablespaces successfully work with pg_rewind. Co-authored-by: Mark Sliva (cherry picked from commit aae20c860a418815850685a2fcbfdcef52628625) --- .../behave/mgmt_utils/gprecoverseg.feature | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/gpMgmt/test/behave/mgmt_utils/gprecoverseg.feature b/gpMgmt/test/behave/mgmt_utils/gprecoverseg.feature index 15e9773ecb..7c676572da 100644 --- a/gpMgmt/test/behave/mgmt_utils/gprecoverseg.feature +++ b/gpMgmt/test/behave/mgmt_utils/gprecoverseg.feature @@ -227,3 +227,41 @@ Feature: gprecoverseg tests And the segments are synchronized # validate the the new segment has the correct setting by getting admin connection to that segment Then the saved primary segment reports the same value for sql "show data_checksums" db "template1" as was saved + + @skip # tablespaces are being reworked and currently do not work with pg_rewind + @concourse_cluster + Scenario: incremental recovery works with tablespaces on a multi-host environment + Given the database is running + And a tablespace is created with data + And user stops all primary processes + And user can start transactions + When the user runs "gprecoverseg -a" + Then gprecoverseg should return a return code of 0 + And the segments are synchronized + And the tablespace is valid + + Given another tablespace is created with data + When the user runs "gprecoverseg -ra" + Then gprecoverseg should return a return code of 0 + And the segments are synchronized + And the tablespace is valid + And the other tablespace is valid + + @skip # tablespaces are being reworked and currently do not work with pg_rewind + @concourse_cluster + Scenario: full recovery works with tablespaces on a multi-host environment + Given the database is running + And a tablespace is created with data + And user stops all primary processes + And user can start transactions + When the user runs "gprecoverseg -a -F" + Then gprecoverseg should return a return code of 0 + And the segments are synchronized + And the tablespace is valid + + Given another tablespace is created with data + When the user runs "gprecoverseg -ra" + Then gprecoverseg should return a return code of 0 + And the segments are synchronized + And the tablespace is valid + And the other tablespace is valid -- GitLab