[07:35:31.672](0.012s) # testing using transfer mode --link # Checking port 63006 # Found port 63006 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=63006 host=/tmp/zxmGXtpVWu Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [07:35:31.703](0.031s) # 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 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: default collation provider: builtin default collation locale: C 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 7072 [07:35:33.745](2.042s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [07:35:33.831](0.086s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [07:35:33.911](0.080s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [07:35:33.995](0.084s) ok 4 - created database with ASCII characters from 91 to 127 [07:35:33.996](0.001s) # running regression tests in old instance # using postmaster on /tmp/zxmGXtpVWu, port 63006 ok 1 - test_setup 617 ms # parallel group (20 tests): varchar char pg_lsn oid txid name uuid int2 boolean money int4 text regproc float4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 224 ms ok 3 + char 99 ms ok 4 + name 174 ms ok 5 + varchar 81 ms ok 6 + text 232 ms ok 7 + int2 206 ms ok 8 + int4 230 ms ok 9 + int8 309 ms ok 10 + oid 143 ms ok 11 + float4 300 ms ok 12 + float8 324 ms ok 13 + bit 322 ms ok 14 + numeric 859 ms ok 15 + txid 161 ms ok 16 + uuid 173 ms ok 17 + enum 342 ms ok 18 + money 229 ms ok 19 + rangetypes 679 ms ok 20 + pg_lsn 137 ms ok 21 + regproc 249 ms # parallel group (20 tests): md5 lseg circle time path line macaddr timetz macaddr8 point numerology polygon inet date box timestamp interval strings timestamptz multirangetypes ok 22 + strings 680 ms ok 23 + md5 111 ms ok 24 + numerology 247 ms ok 25 + point 220 ms ok 26 + lseg 121 ms ok 27 + line 160 ms ok 28 + box 435 ms ok 29 + path 159 ms ok 30 + polygon 291 ms ok 31 + circle 136 ms ok 32 + date 382 ms ok 33 + time 137 ms ok 34 + timetz 177 ms ok 35 + timestamp 558 ms ok 36 + timestamptz 767 ms ok 37 + interval 615 ms ok 38 + inet 307 ms ok 39 + macaddr 162 ms ok 40 + macaddr8 217 ms ok 41 + multirangetypes 825 ms # parallel group (12 tests): comments misc_sanity unicode mvcc tstypes xid expressions horology regex type_sanity geometry opr_sanity ok 42 + geometry 349 ms ok 43 + horology 246 ms ok 44 + tstypes 130 ms ok 45 + regex 270 ms ok 46 + type_sanity 277 ms ok 47 + opr_sanity 491 ms ok 48 + misc_sanity 39 ms ok 49 + comments 37 ms ok 50 + expressions 202 ms ok 51 + unicode 43 ms ok 52 + xid 144 ms ok 53 + mvcc 97 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 344 ms ok 55 + copyselect 148 ms ok 56 + copydml 205 ms ok 57 + insert 1042 ms ok 58 + insert_conflict 745 ms # parallel group (7 tests): create_function_c create_operator create_schema create_misc create_type create_procedure create_table ok 59 + create_function_c 20 ms ok 60 + create_misc 107 ms ok 61 + create_operator 67 ms ok 62 + create_procedure 109 ms ok 63 + create_table 1618 ms ok 64 + create_type 109 ms ok 65 + create_schema 104 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1849 ms ok 67 + create_index_spgist 907 ms ok 68 + create_view 1098 ms ok 69 + index_including 592 ms ok 70 + index_including_gist 464 ms # parallel group (16 tests): hash_func create_cast roleattributes errors create_aggregate drop_if_exists typed_table select create_am create_function_sql infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 250 ms ok 72 + create_function_sql 431 ms ok 73 + create_cast 178 ms ok 74 + constraints 1311 ms ok 75 + triggers 5347 ms ok 76 + select 299 ms ok 77 + inherit 3931 ms ok 78 + typed_table 288 ms ok 79 + vacuum 695 ms ok 80 + drop_if_exists 257 ms ok 81 + updatable_views 2887 ms ok 82 + roleattributes 183 ms ok 83 + create_am 397 ms ok 84 + hash_func 136 ms ok 85 + errors 184 ms ok 86 + infinite_recurse 436 ms ok 87 - sanity_check 207 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit namespace case select_distinct select_into prepared_xacts hash_index union portals subselect arrays transactions update aggregates join btree_index ok 88 + select_into 401 ms ok 89 + select_distinct 360 ms ok 90 + select_distinct_on 146 ms ok 91 + select_implicit 271 ms ok 92 + select_having 184 ms ok 93 + subselect 835 ms ok 94 + union 724 ms ok 95 + case 306 ms ok 96 + join 1889 ms ok 97 + aggregates 1661 ms ok 98 + transactions 887 ms ok 99 + random 195 ms ok 100 + portals 829 ms ok 101 + arrays 864 ms ok 102 + btree_index 1980 ms ok 103 + hash_index 659 ms ok 104 + update 1378 ms ok 105 + delete 176 ms ok 106 + namespace 301 ms ok 107 + prepared_xacts 420 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label password object_address lock replica_identity collate spgist groupingsets gin gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 3646 ms ok 109 + gin 1356 ms ok 110 + gist 1506 ms ok 111 + spgist 1242 ms ok 112 + privileges 4428 ms ok 113 + init_privs 42 ms ok 114 + security_label 486 ms ok 115 + collate 1165 ms ok 116 + matview 1725 ms ok 117 + lock 963 ms ok 118 + replica_identity 1131 ms ok 119 + rowsecurity 4260 ms ok 120 + object_address 881 ms ok 121 + tablesample 427 ms ok 122 + groupingsets 1262 ms ok 123 + drop_operator 126 ms ok 124 + password 686 ms ok 125 + identity 2096 ms ok 126 + generated 2568 ms ok 127 + join_hash 3672 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 148 ms ok 129 + brin_multi 762 ms # parallel group (17 tests): async dbsize sysviews tidrangescan alter_operator tidscan tid tsrf misc incremental_sort misc_functions create_role without_overlaps alter_generic merge collate.icu.utf8 create_table_like ok 130 + create_table_like 1053 ms ok 131 + alter_generic 566 ms ok 132 + alter_operator 219 ms ok 133 + misc 349 ms ok 134 + async 71 ms ok 135 + dbsize 140 ms ok 136 + merge 889 ms ok 137 + misc_functions 389 ms not ok 138 + sysviews 163 ms ok 139 + tsrf 292 ms ok 140 + tid 225 ms ok 141 + tidscan 222 ms ok 142 + tidrangescan 183 ms ok 143 + collate.icu.utf8 937 ms ok 144 + incremental_sort 370 ms ok 145 + create_role 412 ms ok 146 + without_overlaps 499 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 147 + rules 1140 ms ok 148 + psql 1214 ms ok 149 + psql_crosstab 44 ms ok 150 + amutils 34 ms ok 151 + stats_ext 2044 ms ok 152 + collate.linux.utf8 12 ms ok 153 + collate.windows.win1252 17 ms ok 154 - select_parallel 1107 ms ok 155 - write_parallel 508 ms ok 156 - vacuum_parallel 196 ms # parallel group (2 tests): subscription publication ok 157 + publication 1371 ms ok 158 + subscription 278 ms # parallel group (17 tests): advisory_lock xmlmap portals_p2 combocid select_views functional_deps bitmapops tsdicts dependency equivclass indirect_toast guc window cluster tsearch foreign_data foreign_key ok 159 + select_views 360 ms ok 160 + portals_p2 245 ms ok 161 + foreign_key 6963 ms ok 162 + cluster 1247 ms ok 163 + dependency 503 ms ok 164 + guc 601 ms ok 165 + bitmapops 473 ms ok 166 + combocid 344 ms ok 167 + tsearch 1345 ms ok 168 + tsdicts 498 ms ok 169 + foreign_data 3675 ms ok 170 + window 1232 ms ok 171 + xmlmap 228 ms ok 172 + functional_deps 373 ms ok 173 + advisory_lock 192 ms ok 174 + indirect_toast 575 ms ok 175 + equivclass 503 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 365 ms ok 177 + jsonb 637 ms ok 178 + json_encoding 68 ms ok 179 + jsonpath 187 ms ok 180 + jsonpath_encoding 32 ms ok 181 + jsonb_jsonpath 446 ms ok 182 + sqljson 208 ms # parallel group (18 tests): prepare conversion limit returning plancache temp rowtypes sequence truncate with xml copy2 largeobject rangefuncs polymorphism domain plpgsql alter_table ok 183 + plancache 415 ms ok 184 + limit 358 ms ok 185 + plpgsql 2888 ms ok 186 + copy2 1179 ms ok 187 + temp 736 ms ok 188 + domain 1396 ms ok 189 + rangefuncs 1204 ms ok 190 + prepare 157 ms ok 191 + conversion 341 ms ok 192 + truncate 1015 ms ok 193 + alter_table 7935 ms ok 194 + sequence 973 ms ok 195 + polymorphism 1230 ms ok 196 + rowtypes 866 ms ok 197 + returning 407 ms ok 198 + largeobject 1191 ms ok 199 + with 1095 ms ok 200 + xml 1157 ms # parallel group (13 tests): predicate hash_part reloptions partition_info explain memoize compression partition_aggregate tuplesort stats partition_prune partition_join indexing ok 201 + partition_join 4105 ms ok 202 + partition_prune 3813 ms ok 203 + reloptions 301 ms ok 204 + hash_part 182 ms ok 205 + indexing 4672 ms ok 206 + partition_aggregate 1288 ms ok 207 + partition_info 362 ms ok 208 + tuplesort 1856 ms ok 209 + explain 443 ms ok 210 + compression 832 ms ok 211 + memoize 557 ms ok 212 + stats 1914 ms ok 213 + predicate 135 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 411 ms ok 215 + event_trigger 579 ms ok 216 - event_trigger_login 63 ms ok 217 - fast_default 689 ms ok 218 - tablespace 1964 ms 1..218 # 1 of 218 tests failed. # The differences that caused some tests to fail can be viewed in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs". # A copy of the test summary that you see above is saved in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out 2024-03-17 07:34:32.799664000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-17 07:35:54.727780000 +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 === [07:36:24.714](50.718s) not ok 5 - regression tests pass [07:36:24.714](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [07:36:24.715](0.000s) # got: '256' # expected: '0' # Checking port 63007 # Found port 63007 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=63007 host=/tmp/zxmGXtpVWu Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [07:36:24.717](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: default collation 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=63006 host=/tmp/zxmGXtpVWu dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_MG4i/dump1.sql [07:36:30.807](6.089s) 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/zxmGXtpVWu -p 63006 -P 63007 --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 [07:36:30.989](0.182s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [07:36:30.990](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/zxmGXtpVWu -p 63006 -P 63007 --link --check [07:36:31.925](0.935s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [07:36:31.928](0.003s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [07:36:31.928](0.001s) 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 18960 ### 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/zxmGXtpVWu -p 63006 -P 63007 --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* [07:36:33.900](1.972s) ok 12 - run of pg_upgrade --check for new instance [07:36:33.901](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/zxmGXtpVWu -p 63006 -P 63007 --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 [07:36:51.391](17.490s) ok 14 - run of pg_upgrade for new instance [07:36:51.391](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 22383 [07:36:51.514](0.123s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=63007 host=/tmp/zxmGXtpVWu dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_MG4i/dump2.sql [07:36:53.701](2.187s) ok 17 - dump after running pg_upgrade [07:36:53.812](0.111s) ok 18 - old and new dumps match after pg_upgrade [07:36:53.812](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" [07:36:53.940](0.127s) # Looks like you failed 1 test of 18.