[18:10:33.741](0.012s) # testing using transfer mode --link # Checking port 55496 # Found port 55496 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=55496 host=/tmp/aLmXZ8RGzc Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [18:10:33.778](0.038s) # 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 6546 [18:10:35.765](1.986s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [18:10:35.804](0.039s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [18:10:35.894](0.090s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [18:10:35.932](0.038s) ok 4 - created database with ASCII characters from 91 to 127 [18:10:35.932](0.001s) # running regression tests in old instance # using postmaster on /tmp/aLmXZ8RGzc, port 55496 ok 1 - test_setup 499 ms # parallel group (20 tests): varchar pg_lsn char txid name oid text int2 uuid float4 money regproc boolean int4 bit int8 enum float8 rangetypes numeric ok 2 + boolean 326 ms ok 3 + char 149 ms ok 4 + name 173 ms ok 5 + varchar 96 ms ok 6 + text 233 ms ok 7 + int2 264 ms ok 8 + int4 341 ms ok 9 + int8 422 ms ok 10 + oid 193 ms ok 11 + float4 294 ms ok 12 + float8 435 ms ok 13 + bit 398 ms ok 14 + numeric 1006 ms ok 15 + txid 166 ms ok 16 + uuid 272 ms ok 17 + enum 427 ms ok 18 + money 297 ms ok 19 + rangetypes 893 ms ok 20 + pg_lsn 137 ms ok 21 + regproc 313 ms # parallel group (20 tests): lseg path md5 circle time macaddr8 line timetz point macaddr polygon numerology inet date box timestamp strings interval timestamptz multirangetypes ok 22 + strings 724 ms ok 23 + md5 78 ms ok 24 + numerology 266 ms ok 25 + point 200 ms ok 26 + lseg 53 ms ok 27 + line 159 ms ok 28 + box 339 ms ok 29 + path 55 ms ok 30 + polygon 260 ms ok 31 + circle 82 ms ok 32 + date 337 ms ok 33 + time 119 ms ok 34 + timetz 187 ms ok 35 + timestamp 653 ms ok 36 + timestamptz 775 ms ok 37 + interval 734 ms ok 38 + inet 295 ms ok 39 + macaddr 205 ms ok 40 + macaddr8 144 ms ok 41 + multirangetypes 996 ms # parallel group (12 tests): comments misc_sanity unicode mvcc type_sanity xid expressions regex tstypes geometry opr_sanity horology ok 42 + geometry 457 ms ok 43 + horology 525 ms ok 44 + tstypes 418 ms ok 45 + regex 371 ms ok 46 + type_sanity 218 ms ok 47 + opr_sanity 502 ms ok 48 + misc_sanity 69 ms ok 49 + comments 64 ms ok 50 + expressions 269 ms ok 51 + unicode 89 ms ok 52 + xid 234 ms ok 53 + mvcc 119 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 210 ms ok 55 + copyselect 104 ms ok 56 + copydml 134 ms ok 57 + insert 1229 ms ok 58 + insert_conflict 726 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 28 ms ok 60 + create_misc 179 ms ok 61 + create_operator 116 ms ok 62 + create_procedure 186 ms ok 63 + create_table 1213 ms ok 64 + create_type 188 ms ok 65 + create_schema 129 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2500 ms ok 67 + create_index_spgist 1096 ms ok 68 + create_view 1332 ms ok 69 + index_including 821 ms ok 70 + index_including_gist 642 ms # parallel group (16 tests): create_cast hash_func select create_aggregate errors roleattributes infinite_recurse typed_table drop_if_exists create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 260 ms ok 72 + create_function_sql 468 ms ok 73 + create_cast 100 ms ok 74 + constraints 1558 ms not ok 75 + triggers 5950 ms ok 76 + select 230 ms ok 77 + inherit 4128 ms ok 78 + typed_table 413 ms ok 79 + vacuum 1075 ms ok 80 + drop_if_exists 420 ms ok 81 + updatable_views 3699 ms ok 82 + roleattributes 270 ms ok 83 + create_am 457 ms ok 84 + hash_func 157 ms ok 85 + errors 261 ms ok 86 + infinite_recurse 394 ms ok 87 - sanity_check 220 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit case select_into namespace prepared_xacts select_distinct union transactions portals subselect hash_index arrays update aggregates btree_index join ok 88 + select_into 316 ms ok 89 + select_distinct 432 ms ok 90 + select_distinct_on 77 ms ok 91 + select_implicit 208 ms ok 92 + select_having 166 ms ok 93 + subselect 964 ms ok 94 + union 740 ms ok 95 + case 239 ms ok 96 + join 1927 ms ok 97 + aggregates 1723 ms ok 98 + transactions 870 ms ok 99 + random 203 ms ok 100 + portals 937 ms ok 101 + arrays 1108 ms ok 102 + btree_index 1755 ms ok 103 + hash_index 1108 ms ok 104 + update 1333 ms ok 105 + delete 84 ms ok 106 + namespace 354 ms ok 107 + prepared_xacts 388 ms # parallel group (20 tests): init_privs drop_operator security_label password tablesample lock collate spgist object_address replica_identity gin groupingsets gist matview identity privileges generated brin join_hash rowsecurity ok 108 + brin 4014 ms ok 109 + gin 1535 ms ok 110 + gist 1732 ms ok 111 + spgist 1280 ms ok 112 + privileges 3457 ms ok 113 + init_privs 79 ms ok 114 + security_label 493 ms ok 115 + collate 1260 ms ok 116 + matview 2269 ms ok 117 + lock 828 ms ok 118 + replica_identity 1519 ms ok 119 + rowsecurity 4498 ms ok 120 + object_address 1393 ms ok 121 + tablesample 535 ms ok 122 + groupingsets 1656 ms ok 123 + drop_operator 243 ms ok 124 + password 494 ms ok 125 + identity 2711 ms ok 126 + generated 3750 ms ok 127 + join_hash 4084 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 180 ms ok 129 + brin_multi 721 ms # parallel group (18 tests): async dbsize collate.utf8 tidscan sysviews tidrangescan alter_operator tid misc tsrf misc_functions incremental_sort create_role alter_generic collate.icu.utf8 merge create_table_like without_overlaps ok 130 + create_table_like 1121 ms ok 131 + alter_generic 544 ms ok 132 + alter_operator 235 ms ok 133 + misc 295 ms ok 134 + async 66 ms ok 135 + dbsize 125 ms ok 136 + merge 1005 ms ok 137 + misc_functions 393 ms ok 138 + sysviews 175 ms ok 139 + tsrf 313 ms ok 140 + tid 251 ms ok 141 + tidscan 160 ms ok 142 + tidrangescan 233 ms ok 143 + collate.utf8 149 ms ok 144 + collate.icu.utf8 883 ms ok 145 + incremental_sort 418 ms ok 146 + create_role 423 ms ok 147 + without_overlaps 1347 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1535 ms ok 149 + psql 1580 ms ok 150 + psql_crosstab 58 ms ok 151 + amutils 35 ms ok 152 + stats_ext 2382 ms ok 153 + collate.linux.utf8 17 ms ok 154 + collate.windows.win1252 17 ms ok 155 - select_parallel 2200 ms ok 156 - write_parallel 320 ms ok 157 - vacuum_parallel 183 ms # parallel group (2 tests): subscription publication ok 158 + publication 2046 ms ok 159 + subscription 151 ms # parallel group (17 tests): xmlmap advisory_lock portals_p2 combocid functional_deps dependency select_views bitmapops equivclass indirect_toast tsdicts guc cluster window tsearch foreign_data foreign_key ok 160 + select_views 501 ms ok 161 + portals_p2 227 ms ok 162 + foreign_key 6875 ms ok 163 + cluster 1104 ms ok 164 + dependency 410 ms ok 165 + guc 712 ms ok 166 + bitmapops 516 ms ok 167 + combocid 234 ms ok 168 + tsearch 1184 ms ok 169 + tsdicts 610 ms ok 170 + foreign_data 3040 ms ok 171 + window 1129 ms ok 172 + xmlmap 211 ms ok 173 + functional_deps 317 ms ok 174 + advisory_lock 213 ms ok 175 + indirect_toast 609 ms ok 176 + equivclass 527 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 316 ms ok 178 + jsonb 880 ms ok 179 + json_encoding 62 ms ok 180 + jsonpath 169 ms ok 181 + jsonpath_encoding 35 ms ok 182 + jsonb_jsonpath 419 ms ok 183 + sqljson 171 ms ok 184 + sqljson_queryfuncs 259 ms ok 185 + sqljson_jsontable 134 ms # parallel group (18 tests): prepare returning conversion limit plancache temp truncate rowtypes with sequence copy2 polymorphism xml largeobject domain rangefuncs plpgsql alter_table ok 186 + plancache 703 ms ok 187 + limit 565 ms ok 188 + plpgsql 4463 ms ok 189 + copy2 1625 ms ok 190 + temp 888 ms ok 191 + domain 1919 ms ok 192 + rangefuncs 2052 ms ok 193 + prepare 215 ms ok 194 + conversion 438 ms ok 195 + truncate 1293 ms ok 196 + alter_table 9908 ms ok 197 + sequence 1481 ms ok 198 + polymorphism 1677 ms ok 199 + rowtypes 1349 ms ok 200 + returning 379 ms ok 201 + largeobject 1839 ms ok 202 + with 1460 ms ok 203 + xml 1720 ms # parallel group (13 tests): predicate hash_part reloptions explain memoize partition_info compression partition_aggregate tuplesort stats partition_join partition_prune indexing ok 204 + partition_join 4764 ms ok 205 + partition_prune 5177 ms ok 206 + reloptions 392 ms ok 207 + hash_part 223 ms ok 208 + indexing 6648 ms ok 209 + partition_aggregate 1312 ms ok 210 + partition_info 546 ms ok 211 + tuplesort 1557 ms ok 212 + explain 431 ms ok 213 + compression 1257 ms ok 214 + memoize 505 ms ok 215 + stats 1736 ms ok 216 + predicate 133 ms # parallel group (2 tests): oidjoins event_trigger ok 217 + oidjoins 387 ms ok 218 + event_trigger 488 ms ok 219 - event_trigger_login 81 ms ok 220 - fast_default 429 ms ok 221 - tablespace 1314 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/triggers.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/triggers.out --- /tmp/cirrus-ci-build/src/test/regress/expected/triggers.out 2024-04-06 18:09:42.080006000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/triggers.out 2024-04-06 18:10:50.282963000 +0000 @@ -3720,7 +3720,9 @@ -- test who runs deferred trigger functions -- setup create role groot; +WARNING: roles created by regression test cases should have names starting with "regress_" create role outis; +WARNING: roles created by regression test cases should have names starting with "regress_" create function whoami() returns trigger language plpgsql as $$ begin === EOF === [18:11:33.293](57.361s) not ok 5 - regression tests pass [18:11:33.293](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [18:11:33.293](0.000s) # got: '256' # expected: '0' # Checking port 55497 # Found port 55497 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=55497 host=/tmp/aLmXZ8RGzc Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [18:11:33.296](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: 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=55496 host=/tmp/aLmXZ8RGzc dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_YigE/dump1.sql [18:11:38.163](4.867s) 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/aLmXZ8RGzc -p 55496 -P 55497 --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 [18:11:38.340](0.177s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [18:11:38.341](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/aLmXZ8RGzc -p 55496 -P 55497 --link --check [18:11:38.943](0.602s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [18:11:38.944](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [18:11:38.945](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 18901 ### 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/aLmXZ8RGzc -p 55496 -P 55497 --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* [18:11:40.762](1.817s) ok 12 - run of pg_upgrade --check for new instance [18:11:40.763](0.001s) 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/aLmXZ8RGzc -p 55496 -P 55497 --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 [18:12:01.435](20.672s) ok 14 - run of pg_upgrade for new instance [18:12:01.435](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 22686 [18:12:01.563](0.128s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=55497 host=/tmp/aLmXZ8RGzc dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_YigE/dump2.sql [18:12:03.667](2.104s) ok 17 - dump after running pg_upgrade [18:12:03.757](0.090s) ok 18 - old and new dumps match after pg_upgrade [18:12:03.757](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" [18:12:03.865](0.107s) # Looks like you failed 1 test of 18.