[04:31:37.524](0.012s) # testing using transfer mode --link # Checking port 63260 # Found port 63260 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=63260 host=/tmp/gtPS3up0xz Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [04:31:37.529](0.006s) # 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 7977 [04:31:39.091](1.562s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [04:31:39.126](0.034s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [04:31:39.160](0.034s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [04:31:39.195](0.035s) ok 4 - created database with ASCII characters from 91 to 127 [04:31:39.195](0.000s) # running regression tests in old instance # using postmaster on /tmp/gtPS3up0xz, port 63260 ok 1 - test_setup 545 ms # parallel group (20 tests): varchar pg_lsn char oid name uuid txid int2 regproc money boolean text int4 float4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 179 ms ok 3 + char 96 ms ok 4 + name 117 ms ok 5 + varchar 81 ms ok 6 + text 182 ms ok 7 + int2 160 ms ok 8 + int4 185 ms ok 9 + int8 219 ms ok 10 + oid 108 ms ok 11 + float4 190 ms ok 12 + float8 233 ms ok 13 + bit 223 ms ok 14 + numeric 557 ms ok 15 + txid 132 ms ok 16 + uuid 125 ms ok 17 + enum 244 ms ok 18 + money 170 ms not ok 19 + rangetypes 479 ms ok 20 + pg_lsn 92 ms ok 21 + regproc 165 ms # parallel group (20 tests): md5 lseg path circle macaddr line point time timetz numerology macaddr8 date inet polygon interval box strings timestamp multirangetypes timestamptz ok 22 + strings 363 ms ok 23 + md5 52 ms ok 24 + numerology 164 ms ok 25 + point 107 ms ok 26 + lseg 54 ms ok 27 + line 92 ms ok 28 + box 353 ms ok 29 + path 67 ms ok 30 + polygon 232 ms ok 31 + circle 86 ms ok 32 + date 168 ms ok 33 + time 106 ms ok 34 + timetz 134 ms ok 35 + timestamp 420 ms ok 36 + timestamptz 452 ms ok 37 + interval 264 ms ok 38 + inet 223 ms ok 39 + macaddr 89 ms ok 40 + macaddr8 167 ms ok 41 + multirangetypes 444 ms # parallel group (12 tests): misc_sanity comments unicode mvcc expressions xid type_sanity tstypes geometry horology regex opr_sanity ok 42 + geometry 223 ms ok 43 + horology 239 ms ok 44 + tstypes 222 ms ok 45 + regex 300 ms ok 46 + type_sanity 222 ms ok 47 + opr_sanity 328 ms ok 48 + misc_sanity 32 ms ok 49 + comments 35 ms ok 50 + expressions 112 ms ok 51 + unicode 52 ms ok 52 + xid 130 ms ok 53 + mvcc 63 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 340 ms ok 55 + copyselect 225 ms ok 56 + copydml 222 ms ok 57 + insert 842 ms ok 58 + insert_conflict 502 ms # parallel group (7 tests): create_function_c create_type create_schema create_operator create_misc create_procedure create_table ok 59 + create_function_c 20 ms ok 60 + create_misc 98 ms ok 61 + create_operator 84 ms ok 62 + create_procedure 111 ms ok 63 + create_table 1112 ms ok 64 + create_type 82 ms ok 65 + create_schema 83 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1325 ms ok 67 + create_index_spgist 832 ms ok 68 + create_view 909 ms ok 69 + index_including 453 ms ok 70 + index_including_gist 395 ms # parallel group (16 tests): create_cast errors create_aggregate select roleattributes drop_if_exists hash_func create_function_sql create_am typed_table infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 139 ms ok 72 + create_function_sql 292 ms ok 73 + create_cast 74 ms ok 74 + constraints 893 ms ok 75 + triggers 3074 ms ok 76 + select 153 ms ok 77 + inherit 2790 ms ok 78 + typed_table 368 ms ok 79 + vacuum 744 ms ok 80 + drop_if_exists 196 ms ok 81 + updatable_views 2380 ms ok 82 + roleattributes 181 ms ok 83 + create_am 323 ms ok 84 + hash_func 196 ms ok 85 + errors 118 ms ok 86 + infinite_recurse 392 ms ok 87 - sanity_check 99 ms # parallel group (20 tests): select_distinct_on select_having delete random namespace case select_distinct select_implicit select_into prepared_xacts transactions hash_index union portals arrays subselect update aggregates btree_index join ok 88 + select_into 345 ms ok 89 + select_distinct 336 ms ok 90 + select_distinct_on 58 ms ok 91 + select_implicit 340 ms ok 92 + select_having 103 ms ok 93 + subselect 1975 ms ok 94 + union 1596 ms ok 95 + case 329 ms ok 96 + join 2954 ms ok 97 + aggregates 2538 ms ok 98 + transactions 1494 ms ok 99 + random 108 ms ok 100 + portals 1663 ms ok 101 + arrays 1805 ms ok 102 + btree_index 2826 ms ok 103 + hash_index 1545 ms ok 104 + update 2233 ms ok 105 + delete 103 ms ok 106 + namespace 182 ms ok 107 + prepared_xacts 692 ms # parallel group (20 tests): init_privs drop_operator security_label password tablesample groupingsets lock object_address replica_identity collate spgist gist gin matview identity generated rowsecurity join_hash brin privileges ok 108 + brin 2204 ms ok 109 + gin 1238 ms ok 110 + gist 1208 ms ok 111 + spgist 931 ms ok 112 + privileges 2702 ms ok 113 + init_privs 45 ms ok 114 + security_label 238 ms ok 115 + collate 896 ms ok 116 + matview 1441 ms ok 117 + lock 606 ms ok 118 + replica_identity 863 ms ok 119 + rowsecurity 2024 ms ok 120 + object_address 684 ms ok 121 + tablesample 333 ms ok 122 + groupingsets 604 ms ok 123 + drop_operator 116 ms ok 124 + password 297 ms ok 125 + identity 1702 ms ok 126 + generated 1952 ms ok 127 + join_hash 2198 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 130 ms ok 129 + brin_multi 641 ms # parallel group (17 tests): async sysviews dbsize tidscan tidrangescan alter_operator tid misc tsrf misc_functions create_role incremental_sort without_overlaps alter_generic merge create_table_like collate.icu.utf8 ok 130 + create_table_like 841 ms ok 131 + alter_generic 522 ms ok 132 + alter_operator 202 ms ok 133 + misc 275 ms ok 134 + async 110 ms ok 135 + dbsize 126 ms ok 136 + merge 741 ms ok 137 + misc_functions 306 ms ok 138 + sysviews 115 ms ok 139 + tsrf 284 ms ok 140 + tid 218 ms ok 141 + tidscan 189 ms ok 142 + tidrangescan 197 ms ok 143 + collate.icu.utf8 876 ms ok 144 + incremental_sort 449 ms ok 145 + create_role 342 ms ok 146 + without_overlaps 495 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 147 + rules 864 ms ok 148 + psql 800 ms ok 149 + psql_crosstab 52 ms ok 150 + amutils 37 ms ok 151 + stats_ext 1558 ms ok 152 + collate.linux.utf8 22 ms ok 153 + collate.windows.win1252 29 ms ok 154 - select_parallel 585 ms ok 155 - write_parallel 74 ms ok 156 - vacuum_parallel 100 ms # parallel group (2 tests): subscription publication ok 157 + publication 1024 ms ok 158 + subscription 403 ms # parallel group (17 tests): advisory_lock portals_p2 combocid xmlmap bitmapops functional_deps guc select_views dependency tsdicts equivclass indirect_toast tsearch window cluster foreign_data foreign_key ok 159 + select_views 358 ms ok 160 + portals_p2 152 ms ok 161 + foreign_key 2994 ms ok 162 + cluster 873 ms ok 163 + dependency 364 ms ok 164 + guc 330 ms ok 165 + bitmapops 275 ms ok 166 + combocid 199 ms ok 167 + tsearch 616 ms ok 168 + tsdicts 376 ms ok 169 + foreign_data 1372 ms ok 170 + window 762 ms ok 171 + xmlmap 207 ms ok 172 + functional_deps 291 ms ok 173 + advisory_lock 70 ms ok 174 + indirect_toast 432 ms ok 175 + equivclass 400 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 245 ms ok 177 + jsonb 522 ms ok 178 + json_encoding 83 ms ok 179 + jsonpath 116 ms ok 180 + jsonpath_encoding 83 ms ok 181 + jsonb_jsonpath 442 ms ok 182 + sqljson 190 ms # parallel group (18 tests): prepare limit plancache conversion returning temp sequence truncate rowtypes largeobject copy2 with rangefuncs xml polymorphism domain plpgsql alter_table ok 183 + plancache 302 ms ok 184 + limit 300 ms ok 185 + plpgsql 1567 ms ok 186 + copy2 810 ms ok 187 + temp 500 ms ok 188 + domain 987 ms ok 189 + rangefuncs 866 ms ok 190 + prepare 94 ms ok 191 + conversion 337 ms ok 192 + truncate 693 ms ok 193 + alter_table 3655 ms ok 194 + sequence 634 ms ok 195 + polymorphism 949 ms ok 196 + rowtypes 725 ms ok 197 + returning 411 ms ok 198 + largeobject 766 ms ok 199 + with 845 ms ok 200 + xml 904 ms # parallel group (13 tests): predicate hash_part explain reloptions partition_info memoize compression partition_aggregate stats tuplesort partition_prune partition_join indexing ok 201 + partition_join 1839 ms ok 202 + partition_prune 1773 ms ok 203 + reloptions 249 ms ok 204 + hash_part 181 ms ok 205 + indexing 2008 ms ok 206 + partition_aggregate 951 ms ok 207 + partition_info 299 ms ok 208 + tuplesort 1202 ms ok 209 + explain 224 ms ok 210 + compression 599 ms ok 211 + memoize 321 ms ok 212 + stats 1120 ms ok 213 + predicate 86 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 221 ms ok 215 + event_trigger 262 ms ok 216 - event_trigger_login 29 ms ok 217 - fast_default 244 ms ok 218 - tablespace 630 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-03 04:29:32.208475000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/rangetypes.out 2024-03-03 04:31:40.259666000 +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:32:08.914](29.719s) not ok 5 - regression tests pass [04:32:08.914](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [04:32:08.914](0.000s) # got: '256' # expected: '0' # Checking port 63261 # Found port 63261 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=63261 host=/tmp/gtPS3up0xz Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [04:32:08.917](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=63260 host=/tmp/gtPS3up0xz dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_20ik/dump1.sql [04:32:11.855](2.938s) 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/gtPS3up0xz -p 63260 -P 63261 --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:32:11.996](0.141s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [04:32:11.996](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/gtPS3up0xz -p 63260 -P 63261 --link --check [04:32:12.430](0.434s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [04:32:12.431](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [04:32:12.431](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 11456 ### 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/gtPS3up0xz -p 63260 -P 63261 --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:32:13.839](1.408s) ok 12 - run of pg_upgrade --check for new instance [04:32:13.839](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/gtPS3up0xz -p 63260 -P 63261 --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:32:24.184](10.344s) ok 14 - run of pg_upgrade for new instance [04:32:24.184](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 12505 [04:32:24.310](0.126s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=63261 host=/tmp/gtPS3up0xz dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_20ik/dump2.sql [04:32:25.985](1.675s) ok 17 - dump after running pg_upgrade [04:32:26.062](0.077s) ok 18 - old and new dumps match after pg_upgrade [04:32:26.062](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:32:26.169](0.106s) # Looks like you failed 1 test of 18.