[03:39:54.697](0.013s) # testing using transfer mode --link # Checking port 54039 # Found port 54039 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=54039 host=/tmp/91J17H3exe Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [03:39:54.740](0.042s) # 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 7641 [03:39:56.480](1.741s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [03:39:56.642](0.161s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [03:39:56.732](0.090s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [03:39:56.814](0.082s) ok 4 - created database with ASCII characters from 91 to 127 [03:39:56.814](0.000s) # running regression tests in old instance # using postmaster on /tmp/91J17H3exe, port 54039 ok 1 - test_setup 480 ms # parallel group (20 tests): varchar pg_lsn char name txid oid text uuid int2 money boolean int4 float4 regproc bit int8 float8 enum rangetypes numeric ok 2 + boolean 297 ms ok 3 + char 200 ms ok 4 + name 218 ms ok 5 + varchar 175 ms ok 6 + text 254 ms ok 7 + int2 269 ms ok 8 + int4 306 ms ok 9 + int8 349 ms ok 10 + oid 229 ms ok 11 + float4 314 ms ok 12 + float8 352 ms ok 13 + bit 339 ms ok 14 + numeric 1140 ms ok 15 + txid 220 ms ok 16 + uuid 255 ms ok 17 + enum 382 ms ok 18 + money 287 ms ok 19 + rangetypes 962 ms ok 20 + pg_lsn 182 ms ok 21 + regproc 326 ms # parallel group (20 tests): md5 lseg circle path line time point timetz macaddr macaddr8 numerology inet polygon date box interval timestamp strings timestamptz multirangetypes ok 22 + strings 570 ms ok 23 + md5 65 ms ok 24 + numerology 276 ms ok 25 + point 163 ms ok 26 + lseg 80 ms ok 27 + line 109 ms ok 28 + box 448 ms ok 29 + path 102 ms ok 30 + polygon 303 ms ok 31 + circle 93 ms ok 32 + date 304 ms ok 33 + time 122 ms ok 34 + timetz 189 ms ok 35 + timestamp 529 ms ok 36 + timestamptz 600 ms ok 37 + interval 452 ms ok 38 + inet 294 ms ok 39 + macaddr 196 ms ok 40 + macaddr8 256 ms ok 41 + multirangetypes 693 ms # parallel group (12 tests): misc_sanity mvcc unicode comments xid type_sanity expressions regex tstypes geometry opr_sanity horology ok 42 + geometry 448 ms ok 43 + horology 520 ms ok 44 + tstypes 446 ms ok 45 + regex 399 ms ok 46 + type_sanity 307 ms ok 47 + opr_sanity 507 ms ok 48 + misc_sanity 39 ms ok 49 + comments 89 ms ok 50 + expressions 380 ms ok 51 + unicode 85 ms ok 52 + xid 282 ms ok 53 + mvcc 85 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 347 ms ok 55 + copyselect 54 ms ok 56 + copydml 100 ms ok 57 + insert 1296 ms ok 58 + insert_conflict 588 ms # parallel group (7 tests): create_function_c create_misc create_schema create_procedure create_operator create_type create_table ok 59 + create_function_c 19 ms ok 60 + create_misc 129 ms ok 61 + create_operator 145 ms ok 62 + create_procedure 140 ms ok 63 + create_table 1194 ms ok 64 + create_type 153 ms ok 65 + create_schema 130 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2531 ms ok 67 + create_index_spgist 1066 ms ok 68 + create_view 1453 ms ok 69 + index_including 727 ms ok 70 + index_including_gist 580 ms # parallel group (16 tests): create_cast hash_func roleattributes errors create_aggregate typed_table drop_if_exists select create_am infinite_recurse create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 257 ms ok 72 + create_function_sql 417 ms ok 73 + create_cast 115 ms ok 74 + constraints 1388 ms ok 75 + triggers 4262 ms ok 76 + select 331 ms ok 77 + inherit 3719 ms ok 78 + typed_table 303 ms ok 79 + vacuum 1000 ms ok 80 + drop_if_exists 327 ms ok 81 + updatable_views 2138 ms ok 82 + roleattributes 199 ms ok 83 + create_am 376 ms ok 84 + hash_func 157 ms ok 85 + errors 237 ms ok 86 + infinite_recurse 387 ms ok 87 - sanity_check 305 ms # parallel group (20 tests): delete random select_distinct_on select_having select_implicit namespace case prepared_xacts select_distinct select_into union transactions subselect hash_index portals arrays aggregates update btree_index join ok 88 + select_into 841 ms ok 89 + select_distinct 826 ms ok 90 + select_distinct_on 204 ms ok 91 + select_implicit 479 ms ok 92 + select_having 312 ms ok 93 + subselect 1486 ms ok 94 + union 1274 ms ok 95 + case 628 ms ok 96 + join 2884 ms ok 97 + aggregates 1835 ms ok 98 + transactions 1422 ms ok 99 + random 187 ms ok 100 + portals 1605 ms ok 101 + arrays 1636 ms ok 102 + btree_index 2588 ms ok 103 + hash_index 1557 ms ok 104 + update 2179 ms ok 105 + delete 155 ms ok 106 + namespace 496 ms ok 107 + prepared_xacts 737 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label password lock groupingsets object_address collate spgist gin replica_identity gist matview identity brin join_hash rowsecurity generated privileges ok 108 + brin 3842 ms ok 109 + gin 1420 ms ok 110 + gist 1587 ms ok 111 + spgist 1312 ms ok 112 + privileges 4460 ms ok 113 + init_privs 52 ms ok 114 + security_label 475 ms ok 115 + collate 1161 ms ok 116 + matview 1937 ms ok 117 + lock 785 ms ok 118 + replica_identity 1441 ms ok 119 + rowsecurity 3931 ms ok 120 + object_address 935 ms ok 121 + tablesample 338 ms ok 122 + groupingsets 882 ms ok 123 + drop_operator 167 ms ok 124 + password 592 ms ok 125 + identity 2298 ms ok 126 + generated 3935 ms ok 127 + join_hash 3872 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 329 ms ok 129 + brin_multi 1128 ms # parallel group (18 tests): async dbsize sysviews collate.utf8 tidrangescan tid tidscan misc alter_operator tsrf misc_functions incremental_sort create_role alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 1049 ms ok 131 + alter_generic 663 ms ok 132 + alter_operator 309 ms ok 133 + misc 302 ms ok 134 + async 121 ms ok 135 + dbsize 127 ms ok 136 + merge 1095 ms ok 137 + misc_functions 360 ms not ok 138 + sysviews 128 ms ok 139 + tsrf 311 ms ok 140 + tid 215 ms ok 141 + tidscan 252 ms ok 142 + tidrangescan 207 ms ok 143 + collate.utf8 155 ms ok 144 + collate.icu.utf8 989 ms ok 145 + incremental_sort 361 ms ok 146 + create_role 431 ms ok 147 + without_overlaps 1323 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1740 ms ok 149 + psql 1321 ms ok 150 + psql_crosstab 75 ms ok 151 + amutils 33 ms ok 152 + stats_ext 3091 ms ok 153 + collate.linux.utf8 26 ms ok 154 + collate.windows.win1252 13 ms ok 155 - select_parallel 1776 ms ok 156 - write_parallel 321 ms ok 157 - vacuum_parallel 197 ms # parallel group (2 tests): subscription publication ok 158 + publication 2390 ms ok 159 + subscription 669 ms # parallel group (17 tests): advisory_lock portals_p2 functional_deps xmlmap combocid bitmapops dependency equivclass select_views indirect_toast tsdicts guc tsearch window cluster foreign_data foreign_key ok 160 + select_views 456 ms ok 161 + portals_p2 149 ms ok 162 + foreign_key 7000 ms ok 163 + cluster 1186 ms ok 164 + dependency 424 ms ok 165 + guc 560 ms ok 166 + bitmapops 424 ms ok 167 + combocid 323 ms ok 168 + tsearch 1042 ms ok 169 + tsdicts 520 ms ok 170 + foreign_data 3066 ms ok 171 + window 1069 ms ok 172 + xmlmap 288 ms ok 173 + functional_deps 232 ms ok 174 + advisory_lock 115 ms ok 175 + indirect_toast 506 ms ok 176 + equivclass 433 ms # parallel group (8 tests): jsonpath_encoding json_encoding jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 444 ms ok 178 + jsonb 863 ms ok 179 + json_encoding 99 ms ok 180 + jsonpath 137 ms ok 181 + jsonpath_encoding 72 ms ok 182 + jsonb_jsonpath 494 ms ok 183 + sqljson 250 ms ok 184 + sqljson_queryfuncs 324 ms # parallel group (18 tests): prepare returning limit conversion plancache temp rowtypes truncate sequence with largeobject copy2 rangefuncs xml polymorphism domain plpgsql alter_table ok 185 + plancache 523 ms ok 186 + limit 452 ms ok 187 + plpgsql 2800 ms ok 188 + copy2 1257 ms ok 189 + temp 704 ms ok 190 + domain 1622 ms ok 191 + rangefuncs 1299 ms ok 192 + prepare 238 ms ok 193 + conversion 468 ms ok 194 + truncate 1161 ms ok 195 + alter_table 9933 ms ok 196 + sequence 1184 ms ok 197 + polymorphism 1371 ms ok 198 + rowtypes 907 ms ok 199 + returning 322 ms ok 200 + largeobject 1234 ms ok 201 + with 1192 ms ok 202 + xml 1333 ms # parallel group (13 tests): predicate hash_part reloptions partition_info explain memoize compression partition_aggregate stats tuplesort partition_prune partition_join indexing ok 203 + partition_join 4659 ms ok 204 + partition_prune 4238 ms ok 205 + reloptions 127 ms ok 206 + hash_part 76 ms ok 207 + indexing 5217 ms ok 208 + partition_aggregate 2001 ms ok 209 + partition_info 145 ms ok 210 + tuplesort 2611 ms ok 211 + explain 283 ms ok 212 + compression 1673 ms ok 213 + memoize 762 ms ok 214 + stats 2383 ms ok 215 + predicate 53 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 360 ms ok 217 + event_trigger 574 ms ok 218 - event_trigger_login 100 ms ok 219 - fast_default 646 ms ok 220 - tablespace 1232 ms 1..220 # 1 of 220 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-03-25 03:38:33.328817000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-25 03:40:18.506075000 +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 === [03:40:53.428](56.614s) not ok 5 - regression tests pass [03:40:53.429](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [03:40:53.429](0.000s) # got: '256' # expected: '0' # Checking port 54040 # Found port 54040 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=54040 host=/tmp/91J17H3exe Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [03:40:53.432](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=54039 host=/tmp/91J17H3exe dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_b2It/dump1.sql [03:40:58.065](4.633s) 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/91J17H3exe -p 54039 -P 54040 --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 [03:40:58.248](0.183s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [03:40:58.249](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/91J17H3exe -p 54039 -P 54040 --link --check [03:40:58.902](0.653s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [03:40:58.902](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [03:40:58.902](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 19916 ### 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/91J17H3exe -p 54039 -P 54040 --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* [03:41:00.856](1.953s) ok 12 - run of pg_upgrade --check for new instance [03:41:00.856](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/91J17H3exe -p 54039 -P 54040 --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 [03:41:21.445](20.588s) ok 14 - run of pg_upgrade for new instance [03:41:21.445](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 23495 [03:41:21.567](0.122s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=54040 host=/tmp/91J17H3exe dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_b2It/dump2.sql [03:41:23.760](2.192s) ok 17 - dump after running pg_upgrade [03:41:23.838](0.078s) ok 18 - old and new dumps match after pg_upgrade [03:41:23.838](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" [03:41:23.945](0.106s) # Looks like you failed 1 test of 18.