[22:14:33.803](0.013s) # testing using transfer mode --link # Checking port 51569 # Found port 51569 Name: old_node Data directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata Backup directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/backup Archive directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/archives Connection string: port=51569 host=/tmp/y3jSbxyhHT Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [22:14:33.840](0.037s) # initializing database system by running initdb # Running: initdb -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -A trust -N --wal-segsize 1 --allow-group-access --encoding UTF-8 --lc-collate C --lc-ctype C --locale-provider builtin --builtin-locale C.UTF-8 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with this locale configuration: locale provider: builtin default collation: C.UTF-8 LC_COLLATE: C LC_CTYPE: C LC_MESSAGES: C LC_MONETARY: en_US.UTF-8 LC_NUMERIC: en_US.UTF-8 LC_TIME: en_US.UTF-8 The default text search configuration will be set to "english". Data page checksums are disabled. creating directory /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok Sync to disk skipped. The data directory might become corrupt if the operating system crashes. Success. You can now start the database server using: pg_ctl -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l logfile start # Running: /tmp/cirrus-ci-build/build/src/test/regress/pg_regress --config-auth /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata ### Starting node "old_node" # Running: pg_ctl -w -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log -o --cluster-name=old_node start waiting for server to start.... done server started # Postmaster PID for node "old_node" is 7898 [22:14:36.095](2.255s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [22:14:36.140](0.045s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [22:14:36.167](0.027s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [22:14:36.218](0.051s) ok 4 - created database with ASCII characters from 91 to 127 [22:14:36.220](0.002s) # running regression tests in old instance # using postmaster on /tmp/y3jSbxyhHT, port 51569 ok 1 - test_setup 620 ms # parallel group (20 tests): varchar pg_lsn txid char oid name uuid int2 text money float4 boolean int4 regproc enum float8 int8 bit rangetypes numeric ok 2 + boolean 314 ms ok 3 + char 152 ms ok 4 + name 237 ms ok 5 + varchar 122 ms ok 6 + text 274 ms ok 7 + int2 260 ms ok 8 + int4 322 ms ok 9 + int8 440 ms ok 10 + oid 185 ms ok 11 + float4 298 ms ok 12 + float8 436 ms ok 13 + bit 453 ms ok 14 + numeric 1187 ms ok 15 + txid 149 ms ok 16 + uuid 237 ms ok 17 + enum 405 ms ok 18 + money 296 ms ok 19 + rangetypes 1007 ms ok 20 + pg_lsn 134 ms ok 21 + regproc 326 ms # parallel group (20 tests): md5 circle lseg path line macaddr timetz point time macaddr8 polygon inet numerology box date timestamp interval timestamptz strings multirangetypes ok 22 + strings 925 ms ok 23 + md5 94 ms ok 24 + numerology 445 ms ok 25 + point 211 ms ok 26 + lseg 142 ms ok 27 + line 168 ms ok 28 + box 543 ms ok 29 + path 145 ms ok 30 + polygon 431 ms ok 31 + circle 107 ms ok 32 + date 627 ms ok 33 + time 212 ms ok 34 + timetz 196 ms ok 35 + timestamp 638 ms ok 36 + timestamptz 803 ms ok 37 + interval 740 ms ok 38 + inet 434 ms ok 39 + macaddr 195 ms ok 40 + macaddr8 295 ms ok 41 + multirangetypes 1082 ms # parallel group (12 tests): misc_sanity comments unicode mvcc xid expressions tstypes type_sanity horology regex geometry opr_sanity ok 42 + geometry 366 ms ok 43 + horology 351 ms ok 44 + tstypes 266 ms ok 45 + regex 360 ms ok 46 + type_sanity 283 ms ok 47 + opr_sanity 475 ms ok 48 + misc_sanity 54 ms ok 49 + comments 55 ms ok 50 + expressions 252 ms ok 51 + unicode 57 ms ok 52 + xid 228 ms ok 53 + mvcc 106 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 410 ms ok 55 + copyselect 126 ms ok 56 + copydml 193 ms ok 57 + insert 1271 ms ok 58 + insert_conflict 765 ms # parallel group (7 tests): create_function_c create_operator create_schema create_misc create_procedure create_type create_table ok 59 + create_function_c 26 ms ok 60 + create_misc 190 ms ok 61 + create_operator 120 ms ok 62 + create_procedure 199 ms ok 63 + create_table 2183 ms ok 64 + create_type 208 ms ok 65 + create_schema 175 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1755 ms ok 67 + create_index_spgist 846 ms ok 68 + create_view 996 ms ok 69 + index_including 662 ms ok 70 + index_including_gist 450 ms # parallel group (16 tests): create_cast roleattributes create_aggregate errors drop_if_exists hash_func typed_table select infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 244 ms ok 72 + create_function_sql 465 ms ok 73 + create_cast 95 ms ok 74 + constraints 1848 ms ok 75 + triggers 5539 ms ok 76 + select 367 ms ok 77 + inherit 4151 ms ok 78 + typed_table 367 ms ok 79 + vacuum 1261 ms ok 80 + drop_if_exists 283 ms ok 81 + updatable_views 3082 ms ok 82 + roleattributes 232 ms ok 83 + create_am 622 ms ok 84 + hash_func 325 ms ok 85 + errors 258 ms ok 86 + infinite_recurse 428 ms ok 87 - sanity_check 133 ms # parallel group (20 tests): select_distinct_on delete select_having namespace select_implicit random case select_into select_distinct prepared_xacts union subselect portals transactions hash_index arrays update aggregates btree_index join ok 88 + select_into 383 ms ok 89 + select_distinct 433 ms ok 90 + select_distinct_on 54 ms ok 91 + select_implicit 246 ms ok 92 + select_having 157 ms ok 93 + subselect 850 ms ok 94 + union 641 ms ok 95 + case 293 ms ok 96 + join 2181 ms ok 97 + aggregates 1876 ms ok 98 + transactions 1015 ms ok 99 + random 259 ms ok 100 + portals 874 ms ok 101 + arrays 1040 ms ok 102 + btree_index 2009 ms ok 103 + hash_index 1040 ms ok 104 + update 1501 ms ok 105 + delete 110 ms ok 106 + namespace 238 ms ok 107 + prepared_xacts 447 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label password groupingsets lock replica_identity spgist object_address collate gin gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 3617 ms ok 109 + gin 1365 ms ok 110 + gist 1418 ms ok 111 + spgist 1023 ms ok 112 + privileges 4037 ms ok 113 + init_privs 52 ms ok 114 + security_label 446 ms ok 115 + collate 1279 ms ok 116 + matview 1633 ms ok 117 + lock 946 ms ok 118 + replica_identity 993 ms ok 119 + rowsecurity 3983 ms ok 120 + object_address 1106 ms ok 121 + tablesample 379 ms ok 122 + groupingsets 736 ms ok 123 + drop_operator 330 ms ok 124 + password 632 ms ok 125 + identity 1824 ms ok 126 + generated 3546 ms ok 127 + join_hash 3643 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 138 ms ok 129 + brin_multi 939 ms # parallel group (18 tests): async sysviews dbsize collate.utf8 tid tidrangescan tidscan alter_operator tsrf misc create_role misc_functions incremental_sort alter_generic collate.icu.utf8 merge create_table_like without_overlaps ok 130 + create_table_like 1112 ms ok 131 + alter_generic 736 ms ok 132 + alter_operator 295 ms ok 133 + misc 403 ms ok 134 + async 95 ms ok 135 + dbsize 172 ms ok 136 + merge 1054 ms ok 137 + misc_functions 471 ms not ok 138 + sysviews 141 ms ok 139 + tsrf 377 ms ok 140 + tid 218 ms ok 141 + tidscan 270 ms ok 142 + tidrangescan 250 ms ok 143 + collate.utf8 186 ms ok 144 + collate.icu.utf8 963 ms ok 145 + incremental_sort 475 ms ok 146 + create_role 462 ms ok 147 + without_overlaps 1492 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1378 ms ok 149 + psql 1473 ms ok 150 + psql_crosstab 45 ms ok 151 + amutils 29 ms ok 152 + stats_ext 2426 ms ok 153 + collate.linux.utf8 11 ms ok 154 + collate.windows.win1252 19 ms ok 155 - select_parallel 2384 ms ok 156 - write_parallel 242 ms ok 157 - vacuum_parallel 135 ms # parallel group (2 tests): subscription publication ok 158 + publication 1576 ms ok 159 + subscription 143 ms # parallel group (17 tests): portals_p2 advisory_lock combocid functional_deps xmlmap bitmapops dependency indirect_toast select_views equivclass tsdicts guc cluster window tsearch foreign_data foreign_key ok 160 + select_views 688 ms ok 161 + portals_p2 120 ms ok 162 + foreign_key 6625 ms ok 163 + cluster 1450 ms ok 164 + dependency 569 ms ok 165 + guc 855 ms ok 166 + bitmapops 504 ms ok 167 + combocid 300 ms ok 168 + tsearch 1711 ms ok 169 + tsdicts 756 ms ok 170 + foreign_data 2673 ms ok 171 + window 1477 ms ok 172 + xmlmap 480 ms ok 173 + functional_deps 467 ms ok 174 + advisory_lock 129 ms ok 175 + indirect_toast 653 ms ok 176 + equivclass 689 ms # parallel group (9 tests): jsonpath_encoding json_encoding jsonpath sqljson_jsontable sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 329 ms ok 178 + jsonb 1694 ms ok 179 + json_encoding 38 ms ok 180 + jsonpath 95 ms ok 181 + jsonpath_encoding 34 ms ok 182 + jsonb_jsonpath 888 ms ok 183 + sqljson 168 ms ok 184 + sqljson_queryfuncs 296 ms ok 185 + sqljson_jsontable 109 ms # parallel group (18 tests): prepare returning conversion limit plancache temp with truncate rowtypes sequence copy2 polymorphism xml rangefuncs largeobject domain plpgsql alter_table ok 186 + plancache 553 ms ok 187 + limit 497 ms ok 188 + plpgsql 3384 ms ok 189 + copy2 1387 ms ok 190 + temp 831 ms ok 191 + domain 1884 ms ok 192 + rangefuncs 1457 ms ok 193 + prepare 167 ms ok 194 + conversion 488 ms ok 195 + truncate 1066 ms ok 196 + alter_table 9412 ms ok 197 + sequence 1204 ms ok 198 + polymorphism 1391 ms ok 199 + rowtypes 1101 ms ok 200 + returning 459 ms ok 201 + largeobject 1471 ms ok 202 + with 1030 ms ok 203 + xml 1425 ms # parallel group (13 tests): predicate hash_part reloptions explain partition_info memoize compression partition_aggregate stats tuplesort partition_join indexing partition_prune ok 204 + partition_join 3749 ms ok 205 + partition_prune 5060 ms ok 206 + reloptions 191 ms ok 207 + hash_part 188 ms ok 208 + indexing 4499 ms ok 209 + partition_aggregate 1617 ms ok 210 + partition_info 385 ms ok 211 + tuplesort 3145 ms ok 212 + explain 258 ms ok 213 + compression 915 ms ok 214 + memoize 540 ms ok 215 + stats 2404 ms ok 216 + predicate 60 ms # parallel group (2 tests): oidjoins event_trigger ok 217 + oidjoins 453 ms ok 218 + event_trigger 636 ms ok 219 - event_trigger_login 59 ms ok 220 - fast_default 434 ms ok 221 - tablespace 1903 ms 1..221 # 1 of 221 tests failed. # The differences that caused some tests to fail can be viewed in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs". # A copy of the test summary that you see above is saved in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out 2024-04-06 22:12:57.770984000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-04-06 22:14:58.488540000 +0000 @@ -134,7 +134,8 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) + enable_toast_cache | off +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [22:15:32.764](56.544s) not ok 5 - regression tests pass [22:15:32.764](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [22:15:32.764](0.000s) # got: '256' # expected: '0' # Checking port 51570 # Found port 51570 Name: new_node Data directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata Backup directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/backup Archive directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/archives Connection string: port=51570 host=/tmp/y3jSbxyhHT Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [22:15:32.771](0.007s) # initializing database system by running initdb # Running: initdb -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -A trust -N --wal-segsize 1 --allow-group-access --encoding SQL_ASCII --locale-provider libc The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with this locale configuration: locale provider: libc LC_COLLATE: en_US.UTF-8 LC_CTYPE: en_US.UTF-8 LC_MESSAGES: C LC_MONETARY: en_US.UTF-8 LC_NUMERIC: en_US.UTF-8 LC_TIME: en_US.UTF-8 The default text search configuration will be set to "english". Data page checksums are disabled. creating directory /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok Sync to disk skipped. The data directory might become corrupt if the operating system crashes. Success. You can now start the database server using: pg_ctl -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l logfile start # Running: /tmp/cirrus-ci-build/build/src/test/regress/pg_regress --config-auth /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata # Running: pg_dumpall --no-sync -d port=51569 host=/tmp/y3jSbxyhHT dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_UfTK/dump1.sql [22:15:36.591](3.819s) ok 6 - dump before running pg_upgrade ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -m fast stop waiting for server to shut down... done server stopped # No postmaster PID for node "old_node" # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/does/not/exist/ -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/y3jSbxyhHT -p 51569 -P 51570 --link --check check for "/tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/does/not/exist" failed: No such file or directory Failure, exiting [22:15:36.676](0.085s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [22:15:36.676](0.001s) ok 8 - pg_upgrade_output.d/ not removed after pg_upgrade failure # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/y3jSbxyhHT -p 51569 -P 51570 --link --check [22:15:37.365](0.688s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [22:15:37.365](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [22:15:37.365](0.000s) ok 11 - invalid database causes failure stderr /(?^:^$)/ ### Starting node "old_node" # Running: pg_ctl -w -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log -o --cluster-name=old_node start waiting for server to start.... done server started # Postmaster PID for node "old_node" is 19824 ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -m fast stop waiting for server to shut down.... done server stopped # No postmaster PID for node "old_node" # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/y3jSbxyhHT -p 51569 -P 51570 --link --check Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage ok Checking for presence of required libraries ok Checking database user is the install user ok Checking for prepared transactions ok Checking for new cluster tablespace directories ok *Clusters are compatible* [22:15:39.292](1.927s) ok 12 - run of pg_upgrade --check for new instance [22:15:39.293](0.002s) ok 13 - pg_upgrade_output.d/ removed after pg_upgrade --check success # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/y3jSbxyhHT -p 51569 -P 51570 --link Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage ok Creating dump of global objects ok Creating dump of database schemas ok Checking for presence of required libraries ok Checking database user is the install user ok Checking for prepared transactions ok Checking for new cluster tablespace directories ok If pg_upgrade fails after this point, you must re-initdb the new cluster before continuing. Performing Upgrade ------------------ Setting locale and encoding for new cluster ok Analyzing all rows in the new cluster ok Freezing all rows in the new cluster ok Deleting files from new pg_xact ok Copying old pg_xact to new server ok Setting oldest XID for new cluster ok Setting next transaction ID and epoch for new cluster ok Deleting files from new pg_multixact/offsets ok Copying old pg_multixact/offsets to new server ok Deleting files from new pg_multixact/members ok Copying old pg_multixact/members to new server ok Setting next multixact ID and offset for new cluster ok Resetting WAL archives ok Setting frozenxid and minmxid counters in new cluster ok Restoring global objects in the new cluster ok Restoring database schemas in the new cluster ok Adding ".old" suffix to old global/pg_control ok If you want to start the old cluster, you will need to remove the ".old" suffix from /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata/global/pg_control.old. Because "link" mode was used, the old cluster cannot be safely started once the new cluster has been started. Linking user relation files ok Setting next OID for new cluster ok Creating script to delete old cluster ok Checking for extension updates ok Upgrade Complete ---------------- Optimizer statistics are not transferred by pg_upgrade. Once you start the new server, consider running: /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/vacuumdb --all --analyze-in-stages Running this script will delete the old cluster's data files: ./delete_old_cluster.sh [22:15:59.826](20.533s) ok 14 - run of pg_upgrade for new instance [22:15:59.826](0.000s) ok 15 - pg_upgrade_output.d/ removed after pg_upgrade success ### Starting node "new_node" # Running: pg_ctl -w -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log -o --cluster-name=new_node start waiting for server to start.... done server started # Postmaster PID for node "new_node" is 23590 [22:15:59.950](0.124s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=51570 host=/tmp/y3jSbxyhHT dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_UfTK/dump2.sql [22:16:02.157](2.207s) ok 17 - dump after running pg_upgrade [22:16:02.234](0.076s) ok 18 - old and new dumps match after pg_upgrade [22:16:02.234](0.000s) 1..18 ### Stopping node "new_node" using mode immediate # Running: pg_ctl -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -m immediate stop waiting for server to shut down.... done server stopped # No postmaster PID for node "new_node" [22:16:02.345](0.111s) # Looks like you failed 1 test of 18.