[23:47:35.839](0.013s) # testing using transfer mode --link # Checking port 51028 # Found port 51028 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=51028 host=/tmp/oLM8rnS5g9 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [23:47:35.844](0.005s) # 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 --locale C --locale-provider icu --icu-locale fr-CA The files belonging to this database system will be owned by user "postgres". This user must also own the server process. Using language tag "fr-CA" for ICU locale "fr-CA". The database cluster will be initialized with this locale configuration: provider: icu ICU locale: fr-CA LC_COLLATE: C LC_CTYPE: C LC_MESSAGES: C LC_MONETARY: C LC_NUMERIC: C LC_TIME: C 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 5771 [23:47:37.320](1.476s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [23:47:37.354](0.033s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [23:47:37.388](0.034s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [23:47:37.423](0.035s) ok 4 - created database with ASCII characters from 91 to 127 [23:47:37.424](0.000s) # running regression tests in old instance # using postmaster on /tmp/oLM8rnS5g9, port 51028 ok 1 - test_setup 539 ms # parallel group (20 tests): varchar char pg_lsn oid txid name int2 uuid boolean money int4 text float4 regproc int8 float8 bit enum rangetypes numeric ok 2 + boolean 151 ms ok 3 + char 85 ms ok 4 + name 110 ms ok 5 + varchar 79 ms ok 6 + text 162 ms ok 7 + int2 145 ms ok 8 + int4 159 ms ok 9 + int8 187 ms ok 10 + oid 95 ms ok 11 + float4 172 ms ok 12 + float8 217 ms ok 13 + bit 240 ms ok 14 + numeric 530 ms ok 15 + txid 104 ms ok 16 + uuid 145 ms ok 17 + enum 246 ms ok 18 + money 156 ms ok 19 + rangetypes 516 ms ok 20 + pg_lsn 90 ms ok 21 + regproc 172 ms # parallel group (20 tests): lseg md5 path line circle timetz macaddr time numerology point macaddr8 polygon date interval inet box timestamp timestamptz strings multirangetypes ok 22 + strings 560 ms ok 23 + md5 61 ms ok 24 + numerology 179 ms ok 25 + point 219 ms ok 26 + lseg 56 ms ok 27 + line 98 ms ok 28 + box 463 ms ok 29 + path 90 ms ok 30 + polygon 279 ms ok 31 + circle 102 ms ok 32 + date 332 ms ok 33 + time 175 ms ok 34 + timetz 161 ms ok 35 + timestamp 489 ms ok 36 + timestamptz 537 ms ok 37 + interval 335 ms ok 38 + inet 347 ms ok 39 + macaddr 167 ms ok 40 + macaddr8 271 ms ok 41 + multirangetypes 610 ms # parallel group (12 tests): comments misc_sanity unicode mvcc xid type_sanity expressions geometry horology tstypes regex opr_sanity ok 42 + geometry 171 ms ok 43 + horology 197 ms ok 44 + tstypes 215 ms ok 45 + regex 274 ms ok 46 + type_sanity 130 ms ok 47 + opr_sanity 336 ms ok 48 + misc_sanity 42 ms ok 49 + comments 39 ms ok 50 + expressions 136 ms ok 51 + unicode 68 ms ok 52 + xid 111 ms ok 53 + mvcc 96 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 248 ms ok 55 + copyselect 88 ms ok 56 + copydml 93 ms ok 57 + insert 659 ms ok 58 + insert_conflict 396 ms # parallel group (7 tests): create_function_c create_operator create_type create_schema create_misc create_procedure create_table ok 59 + create_function_c 15 ms ok 60 + create_misc 81 ms ok 61 + create_operator 61 ms ok 62 + create_procedure 85 ms ok 63 + create_table 967 ms ok 64 + create_type 63 ms ok 65 + create_schema 80 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1321 ms ok 67 + create_index_spgist 807 ms ok 68 + create_view 880 ms ok 69 + index_including 551 ms ok 70 + index_including_gist 543 ms # parallel group (16 tests): create_cast hash_func roleattributes errors select create_aggregate create_am typed_table drop_if_exists create_function_sql infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 236 ms ok 72 + create_function_sql 416 ms ok 73 + create_cast 90 ms ok 74 + constraints 874 ms ok 75 + triggers 4192 ms ok 76 + select 185 ms ok 77 + inherit 2633 ms ok 78 + typed_table 359 ms ok 79 + vacuum 589 ms ok 80 + drop_if_exists 377 ms ok 81 + updatable_views 2016 ms ok 82 + roleattributes 159 ms ok 83 + create_am 328 ms ok 84 + hash_func 135 ms ok 85 + errors 167 ms ok 86 + infinite_recurse 420 ms ok 87 - sanity_check 122 ms # parallel group (20 tests): delete select_distinct_on random select_having select_implicit namespace case select_into select_distinct prepared_xacts union portals subselect transactions hash_index arrays update aggregates join btree_index ok 88 + select_into 223 ms ok 89 + select_distinct 269 ms ok 90 + select_distinct_on 86 ms ok 91 + select_implicit 134 ms ok 92 + select_having 104 ms ok 93 + subselect 624 ms ok 94 + union 519 ms ok 95 + case 170 ms ok 96 + join 1290 ms ok 97 + aggregates 1166 ms ok 98 + transactions 686 ms ok 99 + random 94 ms ok 100 + portals 595 ms ok 101 + arrays 750 ms ok 102 + btree_index 1314 ms ok 103 + hash_index 747 ms ok 104 + update 922 ms ok 105 + delete 78 ms ok 106 + namespace 139 ms ok 107 + prepared_xacts 273 ms # parallel group (20 tests): init_privs drop_operator password tablesample security_label lock object_address collate replica_identity groupingsets spgist gist gin brin matview identity generated rowsecurity join_hash privileges ok 108 + brin 1321 ms ok 109 + gin 1248 ms ok 110 + gist 1192 ms ok 111 + spgist 1011 ms ok 112 + privileges 2883 ms ok 113 + init_privs 65 ms ok 114 + security_label 365 ms ok 115 + collate 887 ms ok 116 + matview 1401 ms ok 117 + lock 500 ms ok 118 + replica_identity 926 ms ok 119 + rowsecurity 2406 ms ok 120 + object_address 679 ms ok 121 + tablesample 320 ms ok 122 + groupingsets 954 ms ok 123 + drop_operator 131 ms ok 124 + password 276 ms ok 125 + identity 1855 ms ok 126 + generated 2275 ms ok 127 + join_hash 2600 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 122 ms ok 129 + brin_multi 589 ms # parallel group (17 tests): async dbsize sysviews tidscan tidrangescan tid tsrf misc alter_operator misc_functions create_role incremental_sort without_overlaps alter_generic merge collate.icu.utf8 create_table_like ok 130 + create_table_like 669 ms ok 131 + alter_generic 363 ms ok 132 + alter_operator 183 ms ok 133 + misc 178 ms ok 134 + async 41 ms ok 135 + dbsize 45 ms ok 136 + merge 567 ms ok 137 + misc_functions 200 ms not ok 138 + sysviews 92 ms ok 139 + tsrf 160 ms ok 140 + tid 152 ms ok 141 + tidscan 101 ms ok 142 + tidrangescan 113 ms ok 143 + collate.icu.utf8 584 ms ok 144 + incremental_sort 250 ms ok 145 + create_role 233 ms ok 146 + without_overlaps 352 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 147 + rules 819 ms ok 148 + psql 828 ms ok 149 + psql_crosstab 46 ms ok 150 + amutils 27 ms ok 151 + stats_ext 1934 ms ok 152 + collate.linux.utf8 12 ms ok 153 + collate.windows.win1252 18 ms ok 154 - select_parallel 791 ms ok 155 - write_parallel 96 ms ok 156 - vacuum_parallel 83 ms # parallel group (2 tests): subscription publication ok 157 + publication 628 ms ok 158 + subscription 59 ms # parallel group (17 tests): xmlmap portals_p2 advisory_lock bitmapops functional_deps combocid select_views dependency tsdicts indirect_toast equivclass guc window tsearch cluster foreign_data foreign_key ok 159 + select_views 309 ms ok 160 + portals_p2 182 ms ok 161 + foreign_key 3145 ms ok 162 + cluster 812 ms ok 163 + dependency 310 ms ok 164 + guc 417 ms ok 165 + bitmapops 234 ms ok 166 + combocid 260 ms ok 167 + tsearch 695 ms ok 168 + tsdicts 323 ms ok 169 + foreign_data 2253 ms ok 170 + window 642 ms ok 171 + xmlmap 173 ms ok 172 + functional_deps 251 ms ok 173 + advisory_lock 197 ms ok 174 + indirect_toast 379 ms ok 175 + equivclass 387 ms # parallel group (7 tests): json_encoding jsonpath_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 196 ms ok 177 + jsonb 367 ms ok 178 + json_encoding 23 ms ok 179 + jsonpath 61 ms ok 180 + jsonpath_encoding 29 ms ok 181 + jsonb_jsonpath 213 ms ok 182 + sqljson 118 ms # parallel group (18 tests): prepare returning conversion plancache limit temp sequence rowtypes copy2 with truncate largeobject domain rangefuncs polymorphism xml plpgsql alter_table ok 183 + plancache 345 ms ok 184 + limit 349 ms ok 185 + plpgsql 1982 ms ok 186 + copy2 722 ms ok 187 + temp 403 ms ok 188 + domain 886 ms ok 189 + rangefuncs 901 ms ok 190 + prepare 145 ms ok 191 + conversion 246 ms ok 192 + truncate 806 ms ok 193 + alter_table 3590 ms ok 194 + sequence 616 ms ok 195 + polymorphism 910 ms ok 196 + rowtypes 631 ms ok 197 + returning 203 ms ok 198 + largeobject 815 ms ok 199 + with 759 ms ok 200 + xml 910 ms # parallel group (13 tests): predicate hash_part explain reloptions memoize partition_info compression stats partition_aggregate tuplesort partition_prune partition_join indexing ok 201 + partition_join 1567 ms ok 202 + partition_prune 1509 ms ok 203 + reloptions 236 ms ok 204 + hash_part 162 ms ok 205 + indexing 1725 ms ok 206 + partition_aggregate 1001 ms ok 207 + partition_info 261 ms ok 208 + tuplesort 1012 ms ok 209 + explain 198 ms ok 210 + compression 629 ms ok 211 + memoize 242 ms ok 212 + stats 988 ms ok 213 + predicate 95 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 229 ms ok 215 + event_trigger 276 ms ok 216 - event_trigger_login 27 ms ok 217 - fast_default 240 ms ok 218 - tablespace 617 ms 1..218 # 1 of 218 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-02-25 23:46:58.188118000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-02-25 23:47:51.852561000 +0000 @@ -111,6 +111,7 @@ select name, setting from pg_settings where name like 'enable%'; name | setting --------------------------------+--------- + enable_alter_system | on enable_async_append | on enable_bitmapscan | on enable_gathermerge | on @@ -134,7 +135,7 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [23:48:06.064](28.640s) not ok 5 - regression tests pass [23:48:06.064](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [23:48:06.064](0.000s) # got: '256' # expected: '0' # Checking port 51029 # Found port 51029 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=51029 host=/tmp/oLM8rnS5g9 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [23:48:06.067](0.003s) # 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: 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=51028 host=/tmp/oLM8rnS5g9 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_3UsY/dump1.sql [23:48:08.688](2.621s) 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/oLM8rnS5g9 -p 51028 -P 51029 --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 [23:48:08.834](0.146s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [23:48:08.834](0.000s) 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/oLM8rnS5g9 -p 51028 -P 51029 --link --check [23:48:09.263](0.429s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [23:48:09.264](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [23:48:09.264](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 9270 ### 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/oLM8rnS5g9 -p 51028 -P 51029 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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* [23:48:10.672](1.408s) ok 12 - run of pg_upgrade --check for new instance [23:48:10.673](0.000s) 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/oLM8rnS5g9 -p 51028 -P 51029 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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 [23:48:20.516](9.843s) ok 14 - run of pg_upgrade for new instance [23:48:20.516](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 10320 [23:48:20.644](0.128s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=51029 host=/tmp/oLM8rnS5g9 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_3UsY/dump2.sql [23:48:22.349](1.705s) ok 17 - dump after running pg_upgrade [23:48:22.425](0.076s) ok 18 - old and new dumps match after pg_upgrade [23:48:22.426](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" [23:48:22.530](0.105s) # Looks like you failed 1 test of 18.