[04:37:40.957](0.013s) # testing using transfer mode --link # Checking port 62956 # Found port 62956 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=62956 host=/tmp/xWvQMGJA4N Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [04:37:40.964](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_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 7921 [04:37:42.618](1.654s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [04:37:42.698](0.081s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [04:37:42.784](0.086s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [04:37:42.818](0.034s) ok 4 - created database with ASCII characters from 91 to 127 [04:37:42.819](0.001s) # running regression tests in old instance # using postmaster on /tmp/xWvQMGJA4N, port 62956 ok 1 - test_setup 569 ms # parallel group (20 tests): varchar char oid pg_lsn uuid txid name text int2 money int4 regproc float4 boolean float8 bit int8 enum rangetypes numeric ok 2 + boolean 188 ms ok 3 + char 117 ms ok 4 + name 141 ms ok 5 + varchar 79 ms ok 6 + text 154 ms ok 7 + int2 156 ms ok 8 + int4 183 ms ok 9 + int8 229 ms ok 10 + oid 116 ms ok 11 + float4 186 ms ok 12 + float8 222 ms ok 13 + bit 225 ms ok 14 + numeric 666 ms ok 15 + txid 133 ms ok 16 + uuid 127 ms ok 17 + enum 235 ms ok 18 + money 171 ms not ok 19 + rangetypes 626 ms ok 20 + pg_lsn 123 ms ok 21 + regproc 184 ms # parallel group (20 tests): md5 lseg circle path line time point macaddr timetz macaddr8 inet date numerology polygon interval box strings timestamp multirangetypes timestamptz ok 22 + strings 393 ms ok 23 + md5 62 ms ok 24 + numerology 204 ms ok 25 + point 113 ms ok 26 + lseg 76 ms ok 27 + line 107 ms ok 28 + box 328 ms ok 29 + path 81 ms ok 30 + polygon 204 ms ok 31 + circle 75 ms ok 32 + date 198 ms ok 33 + time 111 ms ok 34 + timetz 129 ms ok 35 + timestamp 423 ms ok 36 + timestamptz 467 ms ok 37 + interval 287 ms ok 38 + inet 183 ms ok 39 + macaddr 127 ms ok 40 + macaddr8 162 ms ok 41 + multirangetypes 439 ms # parallel group (12 tests): comments unicode misc_sanity mvcc xid tstypes geometry type_sanity expressions horology regex opr_sanity ok 42 + geometry 195 ms ok 43 + horology 267 ms ok 44 + tstypes 156 ms ok 45 + regex 293 ms ok 46 + type_sanity 212 ms ok 47 + opr_sanity 418 ms ok 48 + misc_sanity 36 ms ok 49 + comments 16 ms ok 50 + expressions 222 ms ok 51 + unicode 35 ms ok 52 + xid 121 ms ok 53 + mvcc 65 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 251 ms ok 55 + copyselect 89 ms ok 56 + copydml 149 ms ok 57 + insert 700 ms ok 58 + insert_conflict 380 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 14 ms ok 60 + create_misc 83 ms ok 61 + create_operator 78 ms ok 62 + create_procedure 91 ms ok 63 + create_table 1123 ms ok 64 + create_type 84 ms ok 65 + create_schema 78 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1239 ms ok 67 + create_index_spgist 731 ms ok 68 + create_view 756 ms ok 69 + index_including 375 ms ok 70 + index_including_gist 348 ms # parallel group (16 tests): errors create_cast roleattributes select hash_func create_aggregate typed_table create_am create_function_sql infinite_recurse drop_if_exists vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 250 ms ok 72 + create_function_sql 351 ms ok 73 + create_cast 192 ms ok 74 + constraints 942 ms ok 75 + triggers 4166 ms ok 76 + select 207 ms ok 77 + inherit 2880 ms ok 78 + typed_table 300 ms ok 79 + vacuum 563 ms ok 80 + drop_if_exists 388 ms ok 81 + updatable_views 2180 ms ok 82 + roleattributes 195 ms ok 83 + create_am 301 ms ok 84 + hash_func 235 ms ok 85 + errors 123 ms ok 86 + infinite_recurse 352 ms ok 87 - sanity_check 210 ms # parallel group (20 tests): select_distinct_on delete random select_having namespace select_implicit select_into case select_distinct prepared_xacts portals union transactions subselect arrays hash_index update aggregates join btree_index ok 88 + select_into 267 ms ok 89 + select_distinct 392 ms ok 90 + select_distinct_on 93 ms ok 91 + select_implicit 220 ms ok 92 + select_having 149 ms ok 93 + subselect 791 ms ok 94 + union 694 ms ok 95 + case 277 ms ok 96 + join 1792 ms ok 97 + aggregates 1633 ms ok 98 + transactions 718 ms ok 99 + random 102 ms ok 100 + portals 601 ms ok 101 + arrays 837 ms ok 102 + btree_index 1890 ms ok 103 + hash_index 1003 ms ok 104 + update 1170 ms ok 105 + delete 101 ms ok 106 + namespace 185 ms ok 107 + prepared_xacts 394 ms # parallel group (20 tests): init_privs drop_operator security_label password tablesample lock groupingsets collate replica_identity object_address spgist gin gist identity matview generated rowsecurity join_hash brin privileges ok 108 + brin 2800 ms ok 109 + gin 1219 ms ok 110 + gist 1281 ms ok 111 + spgist 1013 ms ok 112 + privileges 3104 ms ok 113 + init_privs 83 ms ok 114 + security_label 266 ms ok 115 + collate 938 ms ok 116 + matview 1598 ms ok 117 + lock 609 ms ok 118 + replica_identity 953 ms ok 119 + rowsecurity 2577 ms ok 120 + object_address 968 ms ok 121 + tablesample 372 ms ok 122 + groupingsets 881 ms ok 123 + drop_operator 147 ms ok 124 + password 363 ms ok 125 + identity 1581 ms ok 126 + generated 2497 ms ok 127 + join_hash 2789 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 116 ms ok 129 + brin_multi 626 ms # parallel group (17 tests): async dbsize sysviews tidrangescan tid tidscan tsrf alter_operator misc_functions misc create_role incremental_sort alter_generic without_overlaps merge collate.icu.utf8 create_table_like ok 130 + create_table_like 708 ms ok 131 + alter_generic 405 ms ok 132 + alter_operator 201 ms ok 133 + misc 249 ms ok 134 + async 52 ms ok 135 + dbsize 79 ms ok 136 + merge 611 ms ok 137 + misc_functions 226 ms ok 138 + sysviews 90 ms ok 139 + tsrf 173 ms ok 140 + tid 145 ms ok 141 + tidscan 154 ms ok 142 + tidrangescan 139 ms ok 143 + collate.icu.utf8 661 ms ok 144 + incremental_sort 359 ms ok 145 + create_role 275 ms ok 146 + without_overlaps 429 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 147 + rules 908 ms ok 148 + psql 974 ms ok 149 + psql_crosstab 52 ms ok 150 + amutils 41 ms ok 151 + stats_ext 1673 ms ok 152 + collate.linux.utf8 20 ms ok 153 + collate.windows.win1252 19 ms ok 154 - select_parallel 1255 ms ok 155 - write_parallel 104 ms ok 156 - vacuum_parallel 87 ms # parallel group (2 tests): subscription publication ok 157 + publication 662 ms ok 158 + subscription 89 ms # parallel group (17 tests): advisory_lock portals_p2 xmlmap combocid functional_deps guc select_views bitmapops equivclass tsdicts dependency indirect_toast tsearch window cluster foreign_data foreign_key ok 159 + select_views 355 ms ok 160 + portals_p2 150 ms ok 161 + foreign_key 3309 ms ok 162 + cluster 804 ms ok 163 + dependency 393 ms ok 164 + guc 344 ms ok 165 + bitmapops 357 ms ok 166 + combocid 215 ms ok 167 + tsearch 706 ms ok 168 + tsdicts 383 ms ok 169 + foreign_data 1447 ms ok 170 + window 757 ms ok 171 + xmlmap 177 ms ok 172 + functional_deps 243 ms ok 173 + advisory_lock 135 ms ok 174 + indirect_toast 492 ms ok 175 + equivclass 376 ms # parallel group (7 tests): json_encoding jsonpath_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 178 ms ok 177 + jsonb 388 ms ok 178 + json_encoding 33 ms ok 179 + jsonpath 91 ms ok 180 + jsonpath_encoding 38 ms ok 181 + jsonb_jsonpath 227 ms ok 182 + sqljson 125 ms # parallel group (18 tests): prepare plancache conversion returning limit temp sequence polymorphism truncate copy2 with rowtypes largeobject rangefuncs domain xml plpgsql alter_table ok 183 + plancache 287 ms ok 184 + limit 392 ms ok 185 + plpgsql 1503 ms ok 186 + copy2 755 ms ok 187 + temp 502 ms ok 188 + domain 941 ms ok 189 + rangefuncs 883 ms ok 190 + prepare 126 ms ok 191 + conversion 326 ms ok 192 + truncate 741 ms ok 193 + alter_table 3622 ms ok 194 + sequence 687 ms ok 195 + polymorphism 739 ms ok 196 + rowtypes 798 ms ok 197 + returning 378 ms ok 198 + largeobject 878 ms ok 199 + with 787 ms ok 200 + xml 1027 ms # parallel group (13 tests): predicate hash_part partition_info memoize reloptions explain compression partition_aggregate tuplesort stats partition_prune partition_join indexing ok 201 + partition_join 1703 ms ok 202 + partition_prune 1624 ms ok 203 + reloptions 316 ms ok 204 + hash_part 134 ms ok 205 + indexing 1888 ms ok 206 + partition_aggregate 882 ms ok 207 + partition_info 227 ms ok 208 + tuplesort 1083 ms ok 209 + explain 408 ms ok 210 + compression 571 ms ok 211 + memoize 262 ms ok 212 + stats 1173 ms ok 213 + predicate 83 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 243 ms ok 215 + event_trigger 281 ms ok 216 - event_trigger_login 33 ms ok 217 - fast_default 389 ms ok 218 - tablespace 613 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/rangetypes.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/rangetypes.out --- /tmp/cirrus-ci-build/src/test/regress/expected/rangetypes.out 2024-03-01 04:35:38.573230000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/rangetypes.out 2024-03-01 04:37:44.057823000 +0000 @@ -651,14 +651,7 @@ set enable_hashjoin=f; set enable_mergejoin=t; select * from numrange_test natural join numrange_test2 order by nr; - nr ------------ - empty - (,5) - [1.1,2.2) - [1.1,2.2) -(4 rows) - +ERROR: range types do not match set enable_nestloop to default; set enable_hashjoin to default; set enable_mergejoin to default; === EOF === [04:38:13.394](30.575s) not ok 5 - regression tests pass [04:38:13.394](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [04:38:13.394](0.000s) # got: '256' # expected: '0' # Checking port 62957 # Found port 62957 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=62957 host=/tmp/xWvQMGJA4N Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [04:38:13.399](0.004s) # 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=62956 host=/tmp/xWvQMGJA4N dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_N49C/dump1.sql [04:38:16.125](2.727s) 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/xWvQMGJA4N -p 62956 -P 62957 --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 [04:38:16.267](0.142s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [04:38:16.267](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/xWvQMGJA4N -p 62956 -P 62957 --link --check [04:38:16.721](0.454s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [04:38:16.721](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [04:38:16.722](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 11423 ### 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/xWvQMGJA4N -p 62956 -P 62957 --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* [04:38:18.125](1.403s) ok 12 - run of pg_upgrade --check for new instance [04:38:18.125](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/xWvQMGJA4N -p 62956 -P 62957 --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 [04:38:27.985](9.860s) ok 14 - run of pg_upgrade for new instance [04:38:27.986](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 12458 [04:38:28.110](0.124s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=62957 host=/tmp/xWvQMGJA4N dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_N49C/dump2.sql [04:38:29.790](1.680s) ok 17 - dump after running pg_upgrade [04:38:29.871](0.082s) ok 18 - old and new dumps match after pg_upgrade [04:38:29.872](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" [04:38:29.983](0.111s) # Looks like you failed 1 test of 18.