[00:09:17.789](0.014s) # testing using transfer mode --link # Checking port 61418 # Found port 61418 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=61418 host=/tmp/aWPe2yGML5 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [00:09:17.797](0.008s) # 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 5881 [00:09:19.442](1.645s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [00:09:19.476](0.034s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [00:09:19.636](0.160s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [00:09:19.719](0.083s) ok 4 - created database with ASCII characters from 91 to 127 [00:09:19.720](0.001s) # running regression tests in old instance # using postmaster on /tmp/aWPe2yGML5, port 61418 ok 1 - test_setup 380 ms # parallel group (20 tests): varchar name char pg_lsn txid uuid oid text money regproc int2 int4 boolean int8 bit float4 float8 enum rangetypes numeric ok 2 + boolean 167 ms ok 3 + char 91 ms ok 4 + name 90 ms ok 5 + varchar 85 ms ok 6 + text 126 ms ok 7 + int2 159 ms ok 8 + int4 159 ms ok 9 + int8 189 ms ok 10 + oid 115 ms ok 11 + float4 197 ms ok 12 + float8 208 ms ok 13 + bit 194 ms ok 14 + numeric 568 ms ok 15 + txid 101 ms ok 16 + uuid 107 ms ok 17 + enum 216 ms ok 18 + money 148 ms ok 19 + rangetypes 497 ms ok 20 + pg_lsn 97 ms ok 21 + regproc 156 ms # parallel group (20 tests): lseg md5 circle path macaddr time point timetz line date numerology macaddr8 inet interval polygon box strings timestamp timestamptz multirangetypes ok 22 + strings 412 ms ok 23 + md5 72 ms ok 24 + numerology 171 ms ok 25 + point 89 ms ok 26 + lseg 48 ms ok 27 + line 97 ms ok 28 + box 350 ms ok 29 + path 78 ms ok 30 + polygon 281 ms ok 31 + circle 76 ms ok 32 + date 128 ms ok 33 + time 84 ms ok 34 + timetz 96 ms ok 35 + timestamp 416 ms ok 36 + timestamptz 444 ms ok 37 + interval 269 ms ok 38 + inet 208 ms ok 39 + macaddr 82 ms ok 40 + macaddr8 170 ms ok 41 + multirangetypes 448 ms # parallel group (12 tests): comments misc_sanity unicode xid mvcc expressions type_sanity geometry horology tstypes regex opr_sanity ok 42 + geometry 193 ms ok 43 + horology 194 ms ok 44 + tstypes 218 ms ok 45 + regex 255 ms ok 46 + type_sanity 137 ms ok 47 + opr_sanity 304 ms ok 48 + misc_sanity 33 ms ok 49 + comments 22 ms ok 50 + expressions 117 ms ok 51 + unicode 33 ms ok 52 + xid 63 ms ok 53 + mvcc 65 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 340 ms ok 55 + copyselect 90 ms ok 56 + copydml 203 ms ok 57 + insert 745 ms ok 58 + insert_conflict 497 ms # parallel group (7 tests): create_function_c create_operator create_procedure create_schema create_type create_misc create_table ok 59 + create_function_c 21 ms ok 60 + create_misc 95 ms ok 61 + create_operator 30 ms ok 62 + create_procedure 70 ms ok 63 + create_table 1038 ms ok 64 + create_type 93 ms ok 65 + create_schema 81 ms # parallel group (5 tests): index_including_gist index_including create_view create_index_spgist create_index ok 66 + create_index 1228 ms ok 67 + create_index_spgist 830 ms ok 68 + create_view 788 ms ok 69 + index_including 424 ms ok 70 + index_including_gist 387 ms # parallel group (16 tests): create_cast create_aggregate roleattributes errors select hash_func drop_if_exists infinite_recurse create_function_sql typed_table create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 165 ms ok 72 + create_function_sql 370 ms ok 73 + create_cast 73 ms ok 74 + constraints 953 ms ok 75 + triggers 4209 ms ok 76 + select 198 ms ok 77 + inherit 2819 ms ok 78 + typed_table 369 ms ok 79 + vacuum 673 ms ok 80 + drop_if_exists 234 ms ok 81 + updatable_views 2389 ms ok 82 + roleattributes 168 ms ok 83 + create_am 374 ms ok 84 + hash_func 207 ms ok 85 + errors 187 ms ok 86 + infinite_recurse 363 ms ok 87 - sanity_check 130 ms # parallel group (20 tests): select_distinct_on select_having random delete namespace select_implicit case select_into prepared_xacts select_distinct union portals arrays subselect hash_index transactions update aggregates btree_index join ok 88 + select_into 254 ms ok 89 + select_distinct 366 ms ok 90 + select_distinct_on 80 ms ok 91 + select_implicit 227 ms ok 92 + select_having 99 ms ok 93 + subselect 855 ms ok 94 + union 657 ms ok 95 + case 237 ms ok 96 + join 1547 ms ok 97 + aggregates 1450 ms ok 98 + transactions 872 ms ok 99 + random 107 ms ok 100 + portals 803 ms ok 101 + arrays 838 ms ok 102 + btree_index 1536 ms ok 103 + hash_index 859 ms ok 104 + update 1257 ms ok 105 + delete 114 ms ok 106 + namespace 157 ms ok 107 + prepared_xacts 348 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password object_address lock replica_identity groupingsets collate spgist brin gin gist matview identity generated rowsecurity join_hash privileges ok 108 + brin 1212 ms ok 109 + gin 1275 ms ok 110 + gist 1311 ms ok 111 + spgist 1077 ms ok 112 + privileges 3185 ms ok 113 + init_privs 57 ms ok 114 + security_label 288 ms ok 115 + collate 1019 ms ok 116 + matview 1922 ms ok 117 + lock 815 ms ok 118 + replica_identity 983 ms ok 119 + rowsecurity 2748 ms ok 120 + object_address 794 ms ok 121 + tablesample 366 ms ok 122 + groupingsets 1006 ms ok 123 + drop_operator 173 ms ok 124 + password 452 ms ok 125 + identity 2046 ms ok 126 + generated 2550 ms ok 127 + join_hash 2952 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 112 ms ok 129 + brin_multi 620 ms # parallel group (17 tests): async dbsize sysviews tidrangescan tidscan tid alter_operator tsrf misc_functions misc incremental_sort create_role without_overlaps alter_generic merge collate.icu.utf8 create_table_like ok 130 + create_table_like 783 ms ok 131 + alter_generic 407 ms ok 132 + alter_operator 234 ms ok 133 + misc 301 ms ok 134 + async 44 ms ok 135 + dbsize 96 ms ok 136 + merge 742 ms ok 137 + misc_functions 272 ms not ok 138 + sysviews 97 ms ok 139 + tsrf 239 ms ok 140 + tid 201 ms ok 141 + tidscan 185 ms ok 142 + tidrangescan 164 ms ok 143 + collate.icu.utf8 763 ms ok 144 + incremental_sort 321 ms ok 145 + create_role 345 ms ok 146 + without_overlaps 399 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 147 + rules 912 ms ok 148 + psql 896 ms ok 149 + psql_crosstab 52 ms ok 150 + amutils 36 ms ok 151 + stats_ext 2090 ms ok 152 + collate.linux.utf8 21 ms ok 153 + collate.windows.win1252 25 ms ok 154 - select_parallel 674 ms ok 155 - write_parallel 79 ms ok 156 - vacuum_parallel 82 ms # parallel group (2 tests): subscription publication ok 157 + publication 643 ms ok 158 + subscription 68 ms # parallel group (17 tests): advisory_lock portals_p2 xmlmap dependency select_views functional_deps guc combocid bitmapops equivclass tsdicts indirect_toast window cluster tsearch foreign_data foreign_key ok 159 + select_views 268 ms ok 160 + portals_p2 87 ms ok 161 + foreign_key 3231 ms ok 162 + cluster 734 ms ok 163 + dependency 252 ms ok 164 + guc 305 ms ok 165 + bitmapops 319 ms ok 166 + combocid 314 ms ok 167 + tsearch 990 ms ok 168 + tsdicts 360 ms ok 169 + foreign_data 2239 ms ok 170 + window 683 ms ok 171 + xmlmap 220 ms ok 172 + functional_deps 266 ms ok 173 + advisory_lock 80 ms ok 174 + indirect_toast 440 ms ok 175 + equivclass 330 ms # parallel group (7 tests): jsonpath_encoding json_encoding sqljson jsonpath json jsonb_jsonpath jsonb ok 176 + json 188 ms ok 177 + jsonb 373 ms ok 178 + json_encoding 33 ms ok 179 + jsonpath 122 ms ok 180 + jsonpath_encoding 28 ms ok 181 + jsonb_jsonpath 238 ms ok 182 + sqljson 118 ms # parallel group (18 tests): prepare conversion returning limit temp plancache polymorphism with truncate copy2 rowtypes rangefuncs largeobject sequence xml domain plpgsql alter_table ok 183 + plancache 477 ms ok 184 + limit 393 ms ok 185 + plpgsql 1371 ms ok 186 + copy2 776 ms ok 187 + temp 467 ms ok 188 + domain 952 ms ok 189 + rangefuncs 823 ms ok 190 + prepare 156 ms ok 191 + conversion 255 ms ok 192 + truncate 757 ms ok 193 + alter_table 3442 ms ok 194 + sequence 912 ms ok 195 + polymorphism 697 ms ok 196 + rowtypes 797 ms ok 197 + returning 380 ms ok 198 + largeobject 841 ms ok 199 + with 722 ms ok 200 + xml 940 ms # parallel group (13 tests): predicate hash_part partition_info reloptions memoize explain compression tuplesort partition_aggregate stats partition_join partition_prune indexing ok 201 + partition_join 1473 ms ok 202 + partition_prune 1527 ms ok 203 + reloptions 267 ms ok 204 + hash_part 131 ms ok 205 + indexing 1718 ms ok 206 + partition_aggregate 967 ms ok 207 + partition_info 228 ms ok 208 + tuplesort 893 ms ok 209 + explain 398 ms ok 210 + compression 632 ms ok 211 + memoize 347 ms ok 212 + stats 1030 ms ok 213 + predicate 96 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 259 ms ok 215 + event_trigger 342 ms ok 216 - event_trigger_login 24 ms ok 217 - fast_default 232 ms ok 218 - tablespace 626 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-01 00:08:24.942194000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-01 00:09:34.471836000 +0000 @@ -111,6 +111,7 @@ select name, setting from pg_settings where name like 'enable%'; name | setting --------------------------------+--------- + enable_alter_system | on enable_async_append | on enable_bitmapscan | on enable_gathermerge | on @@ -134,7 +135,7 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [00:09:48.837](29.117s) not ok 5 - regression tests pass [00:09:48.837](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [00:09:48.837](0.000s) # got: '256' # expected: '0' # Checking port 61419 # Found port 61419 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=61419 host=/tmp/aWPe2yGML5 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [00:09:48.841](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=61418 host=/tmp/aWPe2yGML5 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jkjY/dump1.sql [00:09:51.400](2.559s) 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/aWPe2yGML5 -p 61418 -P 61419 --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 [00:09:51.543](0.143s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [00:09:51.543](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/aWPe2yGML5 -p 61418 -P 61419 --link --check [00:09:51.946](0.403s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [00:09:51.946](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [00:09:51.946](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 9389 ### 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/aWPe2yGML5 -p 61418 -P 61419 --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* [00:09:53.347](1.401s) ok 12 - run of pg_upgrade --check for new instance [00:09:53.347](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/aWPe2yGML5 -p 61418 -P 61419 --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 [00:10:02.680](9.333s) ok 14 - run of pg_upgrade for new instance [00:10:02.680](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 10417 [00:10:02.802](0.122s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=61419 host=/tmp/aWPe2yGML5 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jkjY/dump2.sql [00:10:04.480](1.678s) ok 17 - dump after running pg_upgrade [00:10:04.551](0.070s) ok 18 - old and new dumps match after pg_upgrade [00:10:04.551](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" [00:10:04.655](0.104s) # Looks like you failed 1 test of 18.