[19:09:06.371](0.013s) # testing using transfer mode --link # Checking port 49506 # Found port 49506 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=49506 host=/tmp/dCg6QNFgpX Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [19:09:06.377](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 6509 [19:09:08.025](1.648s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [19:09:08.059](0.033s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [19:09:08.141](0.083s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [19:09:08.311](0.169s) ok 4 - created database with ASCII characters from 91 to 127 [19:09:08.311](0.001s) # running regression tests in old instance # using postmaster on /tmp/dCg6QNFgpX, port 49506 ok 1 - test_setup 320 ms # parallel group (20 tests): varchar pg_lsn char txid name text uuid oid int2 regproc float4 money boolean int4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 166 ms ok 3 + char 97 ms ok 4 + name 125 ms ok 5 + varchar 74 ms ok 6 + text 136 ms ok 7 + int2 139 ms ok 8 + int4 168 ms ok 9 + int8 182 ms ok 10 + oid 137 ms ok 11 + float4 155 ms ok 12 + float8 203 ms ok 13 + bit 190 ms ok 14 + numeric 596 ms ok 15 + txid 108 ms ok 16 + uuid 136 ms ok 17 + enum 210 ms ok 18 + money 159 ms ok 19 + rangetypes 523 ms ok 20 + pg_lsn 79 ms ok 21 + regproc 145 ms # parallel group (20 tests): md5 path lseg circle timetz time line macaddr point numerology macaddr8 inet date polygon interval box strings timestamp multirangetypes timestamptz ok 22 + strings 359 ms ok 23 + md5 45 ms ok 24 + numerology 161 ms ok 25 + point 117 ms ok 26 + lseg 68 ms ok 27 + line 97 ms ok 28 + box 351 ms ok 29 + path 60 ms ok 30 + polygon 231 ms ok 31 + circle 79 ms ok 32 + date 177 ms ok 33 + time 91 ms ok 34 + timetz 88 ms ok 35 + timestamp 424 ms ok 36 + timestamptz 462 ms ok 37 + interval 287 ms ok 38 + inet 172 ms ok 39 + macaddr 98 ms ok 40 + macaddr8 165 ms ok 41 + multirangetypes 439 ms # parallel group (12 tests): comments misc_sanity mvcc unicode type_sanity expressions xid tstypes geometry horology regex opr_sanity ok 42 + geometry 220 ms ok 43 + horology 249 ms ok 44 + tstypes 204 ms ok 45 + regex 259 ms ok 46 + type_sanity 138 ms ok 47 + opr_sanity 313 ms ok 48 + misc_sanity 43 ms ok 49 + comments 26 ms ok 50 + expressions 138 ms ok 51 + unicode 63 ms ok 52 + xid 151 ms ok 53 + mvcc 57 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 238 ms ok 55 + copyselect 78 ms ok 56 + copydml 97 ms ok 57 + insert 826 ms ok 58 + insert_conflict 517 ms # parallel group (7 tests): create_function_c create_operator create_type create_procedure create_schema create_misc create_table ok 59 + create_function_c 17 ms ok 60 + create_misc 99 ms ok 61 + create_operator 68 ms ok 62 + create_procedure 94 ms ok 63 + create_table 1042 ms ok 64 + create_type 79 ms ok 65 + create_schema 94 ms # parallel group (5 tests): index_including_gist index_including create_view create_index_spgist create_index ok 66 + create_index 1337 ms ok 67 + create_index_spgist 1021 ms ok 68 + create_view 802 ms ok 69 + index_including 596 ms ok 70 + index_including_gist 440 ms # parallel group (16 tests): hash_func create_cast roleattributes select errors create_aggregate drop_if_exists create_am typed_table infinite_recurse create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 224 ms ok 72 + create_function_sql 411 ms ok 73 + create_cast 172 ms ok 74 + constraints 1007 ms not ok 75 + triggers 4441 ms ok 76 + select 222 ms ok 77 + inherit 2801 ms ok 78 + typed_table 331 ms ok 79 + vacuum 576 ms ok 80 + drop_if_exists 308 ms ok 81 + updatable_views 2247 ms ok 82 + roleattributes 188 ms ok 83 + create_am 311 ms ok 84 + hash_func 129 ms ok 85 + errors 221 ms ok 86 + infinite_recurse 392 ms ok 87 - sanity_check 123 ms # parallel group (20 tests): select_distinct_on random select_having delete select_implicit namespace case select_into select_distinct prepared_xacts union transactions portals hash_index subselect arrays update aggregates join btree_index ok 88 + select_into 218 ms ok 89 + select_distinct 268 ms ok 90 + select_distinct_on 74 ms ok 91 + select_implicit 157 ms ok 92 + select_having 99 ms ok 93 + subselect 786 ms ok 94 + union 468 ms ok 95 + case 216 ms ok 96 + join 1343 ms ok 97 + aggregates 1179 ms ok 98 + transactions 667 ms ok 99 + random 96 ms ok 100 + portals 677 ms ok 101 + arrays 806 ms ok 102 + btree_index 1431 ms ok 103 + hash_index 719 ms ok 104 + update 973 ms ok 105 + delete 130 ms ok 106 + namespace 175 ms ok 107 + prepared_xacts 315 ms # parallel group (20 tests): drop_operator init_privs password security_label tablesample object_address lock groupingsets spgist collate replica_identity gin gist brin matview identity generated rowsecurity join_hash privileges ok 108 + brin 1787 ms ok 109 + gin 1272 ms ok 110 + gist 1284 ms ok 111 + spgist 1026 ms ok 112 + privileges 3254 ms ok 113 + init_privs 83 ms ok 114 + security_label 387 ms ok 115 + collate 1103 ms ok 116 + matview 1851 ms ok 117 + lock 978 ms ok 118 + replica_identity 1145 ms ok 119 + rowsecurity 2677 ms ok 120 + object_address 830 ms ok 121 + tablesample 430 ms ok 122 + groupingsets 1007 ms ok 123 + drop_operator 71 ms ok 124 + password 228 ms ok 125 + identity 2110 ms ok 126 + generated 2399 ms ok 127 + join_hash 3026 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 116 ms ok 129 + brin_multi 622 ms # parallel group (17 tests): async dbsize sysviews tidrangescan tid tidscan alter_operator misc misc_functions tsrf create_role incremental_sort without_overlaps alter_generic collate.icu.utf8 merge create_table_like ok 130 + create_table_like 834 ms ok 131 + alter_generic 491 ms ok 132 + alter_operator 250 ms ok 133 + misc 262 ms ok 134 + async 67 ms ok 135 + dbsize 100 ms ok 136 + merge 805 ms ok 137 + misc_functions 264 ms ok 138 + sysviews 104 ms ok 139 + tsrf 267 ms ok 140 + tid 190 ms ok 141 + tidscan 202 ms ok 142 + tidrangescan 135 ms ok 143 + collate.icu.utf8 750 ms ok 144 + incremental_sort 396 ms ok 145 + create_role 315 ms ok 146 + without_overlaps 471 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 147 + rules 915 ms ok 148 + psql 809 ms ok 149 + psql_crosstab 61 ms ok 150 + amutils 46 ms ok 151 + stats_ext 2097 ms ok 152 + collate.linux.utf8 25 ms ok 153 + collate.windows.win1252 30 ms ok 154 - select_parallel 681 ms ok 155 - write_parallel 85 ms ok 156 - vacuum_parallel 88 ms # parallel group (2 tests): subscription publication ok 157 + publication 716 ms ok 158 + subscription 68 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap functional_deps dependency combocid bitmapops select_views tsdicts equivclass guc indirect_toast cluster window tsearch foreign_data foreign_key ok 159 + select_views 328 ms ok 160 + portals_p2 121 ms ok 161 + foreign_key 3042 ms ok 162 + cluster 1178 ms ok 163 + dependency 296 ms ok 164 + guc 457 ms ok 165 + bitmapops 323 ms ok 166 + combocid 308 ms ok 167 + tsearch 1533 ms ok 168 + tsdicts 402 ms ok 169 + foreign_data 2189 ms ok 170 + window 1214 ms ok 171 + xmlmap 181 ms ok 172 + functional_deps 236 ms ok 173 + advisory_lock 142 ms ok 174 + indirect_toast 462 ms ok 175 + equivclass 435 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 265 ms ok 177 + jsonb 480 ms ok 178 + json_encoding 88 ms ok 179 + jsonpath 198 ms ok 180 + jsonpath_encoding 24 ms ok 181 + jsonb_jsonpath 303 ms ok 182 + sqljson 204 ms # parallel group (18 tests): prepare returning conversion limit plancache temp sequence truncate with largeobject rangefuncs polymorphism copy2 xml rowtypes domain plpgsql alter_table ok 183 + plancache 309 ms ok 184 + limit 299 ms ok 185 + plpgsql 2539 ms ok 186 + copy2 898 ms ok 187 + temp 495 ms ok 188 + domain 973 ms ok 189 + rangefuncs 862 ms ok 190 + prepare 95 ms ok 191 + conversion 271 ms ok 192 + truncate 759 ms ok 193 + alter_table 3701 ms ok 194 + sequence 646 ms ok 195 + polymorphism 893 ms ok 196 + rowtypes 920 ms ok 197 + returning 219 ms ok 198 + largeobject 775 ms ok 199 + with 767 ms ok 200 + xml 910 ms # parallel group (13 tests): predicate hash_part partition_info reloptions explain memoize compression partition_aggregate tuplesort stats partition_prune partition_join indexing ok 201 + partition_join 1882 ms ok 202 + partition_prune 1714 ms ok 203 + reloptions 286 ms ok 204 + hash_part 174 ms ok 205 + indexing 2032 ms ok 206 + partition_aggregate 949 ms ok 207 + partition_info 211 ms ok 208 + tuplesort 1025 ms ok 209 + explain 315 ms ok 210 + compression 512 ms ok 211 + memoize 362 ms ok 212 + stats 1261 ms ok 213 + predicate 94 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 235 ms ok 215 + event_trigger 277 ms ok 216 - event_trigger_login 32 ms ok 217 - fast_default 263 ms ok 218 - tablespace 602 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/triggers.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/triggers.out --- /tmp/cirrus-ci-build/src/test/regress/expected/triggers.out 2024-03-08 19:07:55.931410000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/triggers.out 2024-03-08 19:09:17.807893000 +0000 @@ -3720,7 +3720,9 @@ -- test who runs deferred trigger functions -- setup create role groot; +WARNING: roles created by regression test cases should have names starting with "regress_" create role outis; +WARNING: roles created by regression test cases should have names starting with "regress_" create function whoami() returns trigger language plpgsql as $$ begin === EOF === [19:09:38.367](30.056s) not ok 5 - regression tests pass [19:09:38.367](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [19:09:38.368](0.000s) # got: '256' # expected: '0' # Checking port 49507 # Found port 49507 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=49507 host=/tmp/dCg6QNFgpX Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [19:09:38.371](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=49506 host=/tmp/dCg6QNFgpX dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_t2Bh/dump1.sql [19:09:41.075](2.704s) 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/dCg6QNFgpX -p 49506 -P 49507 --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 [19:09:41.221](0.146s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [19:09:41.221](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/dCg6QNFgpX -p 49506 -P 49507 --link --check [19:09:41.657](0.435s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [19:09:41.657](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [19:09:41.657](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 10040 ### 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/dCg6QNFgpX -p 49506 -P 49507 --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* [19:09:43.572](1.914s) ok 12 - run of pg_upgrade --check for new instance [19:09:43.572](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/dCg6QNFgpX -p 49506 -P 49507 --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 [19:09:53.961](10.390s) ok 14 - run of pg_upgrade for new instance [19:09:53.962](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 11082 [19:09:54.092](0.130s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=49507 host=/tmp/dCg6QNFgpX dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_t2Bh/dump2.sql [19:09:55.772](1.680s) ok 17 - dump after running pg_upgrade [19:09:55.856](0.084s) ok 18 - old and new dumps match after pg_upgrade [19:09:55.856](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" [19:09:55.964](0.107s) # Looks like you failed 1 test of 18.