[08:05:47.529](0.022s) # testing using transfer mode --link # Checking port 50714 # Found port 50714 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=50714 host=/tmp/40eChDb3DU Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [08:05:47.554](0.025s) # 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.UTF-8 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: locale provider: builtin default collation: C.UTF-8 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 8349 [08:05:49.844](2.290s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [08:05:50.009](0.165s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [08:05:50.091](0.082s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [08:05:50.256](0.165s) ok 4 - created database with ASCII characters from 91 to 127 [08:05:50.257](0.001s) # running regression tests in old instance # using postmaster on /tmp/40eChDb3DU, port 50714 ok 1 - test_setup 400 ms # parallel group (20 tests): varchar char name pg_lsn oid txid int2 uuid text int4 regproc float4 boolean money int8 bit float8 enum rangetypes numeric ok 2 + boolean 270 ms ok 3 + char 153 ms ok 4 + name 154 ms ok 5 + varchar 121 ms ok 6 + text 228 ms ok 7 + int2 200 ms ok 8 + int4 232 ms ok 9 + int8 301 ms ok 10 + oid 165 ms ok 11 + float4 256 ms ok 12 + float8 347 ms ok 13 + bit 324 ms ok 14 + numeric 906 ms ok 15 + txid 176 ms ok 16 + uuid 201 ms ok 17 + enum 384 ms ok 18 + money 276 ms ok 19 + rangetypes 775 ms ok 20 + pg_lsn 162 ms ok 21 + regproc 241 ms # parallel group (20 tests): md5 lseg circle macaddr line path point time timetz macaddr8 numerology polygon inet date box interval timestamp timestamptz strings multirangetypes ok 22 + strings 669 ms ok 23 + md5 73 ms ok 24 + numerology 264 ms ok 25 + point 149 ms ok 26 + lseg 100 ms ok 27 + line 138 ms ok 28 + box 443 ms ok 29 + path 141 ms ok 30 + polygon 336 ms ok 31 + circle 105 ms ok 32 + date 382 ms ok 33 + time 154 ms ok 34 + timetz 166 ms ok 35 + timestamp 539 ms ok 36 + timestamptz 667 ms ok 37 + interval 531 ms ok 38 + inet 356 ms ok 39 + macaddr 129 ms ok 40 + macaddr8 227 ms ok 41 + multirangetypes 833 ms # parallel group (12 tests): comments misc_sanity mvcc unicode type_sanity expressions xid tstypes regex geometry horology opr_sanity ok 42 + geometry 423 ms ok 43 + horology 489 ms ok 44 + tstypes 399 ms ok 45 + regex 406 ms ok 46 + type_sanity 206 ms ok 47 + opr_sanity 499 ms ok 48 + misc_sanity 48 ms ok 49 + comments 47 ms ok 50 + expressions 252 ms ok 51 + unicode 147 ms ok 52 + xid 303 ms ok 53 + mvcc 100 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 498 ms ok 55 + copyselect 154 ms ok 56 + copydml 254 ms ok 57 + insert 1127 ms ok 58 + insert_conflict 780 ms # parallel group (7 tests): create_function_c create_operator create_misc create_type create_schema create_procedure create_table ok 59 + create_function_c 67 ms ok 60 + create_misc 132 ms ok 61 + create_operator 126 ms ok 62 + create_procedure 170 ms ok 63 + create_table 1758 ms ok 64 + create_type 136 ms ok 65 + create_schema 167 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1795 ms ok 67 + create_index_spgist 753 ms ok 68 + create_view 925 ms ok 69 + index_including 455 ms ok 70 + index_including_gist 396 ms # parallel group (16 tests): create_cast roleattributes hash_func create_aggregate errors infinite_recurse drop_if_exists typed_table select create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 236 ms ok 72 + create_function_sql 533 ms ok 73 + create_cast 107 ms ok 74 + constraints 1919 ms ok 75 + triggers 6534 ms ok 76 + select 430 ms ok 77 + inherit 4220 ms ok 78 + typed_table 418 ms ok 79 + vacuum 940 ms ok 80 + drop_if_exists 408 ms ok 81 + updatable_views 2558 ms ok 82 + roleattributes 184 ms ok 83 + create_am 479 ms ok 84 + hash_func 204 ms ok 85 + errors 253 ms ok 86 + infinite_recurse 339 ms ok 87 - sanity_check 133 ms # parallel group (20 tests): select_distinct_on delete random select_having select_implicit namespace select_into case prepared_xacts select_distinct union subselect portals hash_index transactions arrays update aggregates btree_index join ok 88 + select_into 320 ms ok 89 + select_distinct 595 ms ok 90 + select_distinct_on 74 ms ok 91 + select_implicit 243 ms ok 92 + select_having 211 ms ok 93 + subselect 901 ms ok 94 + union 629 ms ok 95 + case 365 ms ok 96 + join 2245 ms ok 97 + aggregates 1782 ms ok 98 + transactions 1181 ms ok 99 + random 121 ms ok 100 + portals 996 ms ok 101 + arrays 1357 ms ok 102 + btree_index 2111 ms ok 103 + hash_index 1018 ms ok 104 + update 1482 ms ok 105 + delete 113 ms ok 106 + namespace 300 ms ok 107 + prepared_xacts 587 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock spgist object_address groupingsets collate replica_identity gin gist matview identity brin generated join_hash privileges rowsecurity ok 108 + brin 3767 ms ok 109 + gin 1522 ms ok 110 + gist 1581 ms ok 111 + spgist 1110 ms ok 112 + privileges 4549 ms ok 113 + init_privs 73 ms ok 114 + security_label 285 ms ok 115 + collate 1289 ms ok 116 + matview 1909 ms ok 117 + lock 1090 ms ok 118 + replica_identity 1382 ms ok 119 + rowsecurity 4713 ms ok 120 + object_address 1157 ms ok 121 + tablesample 316 ms ok 122 + groupingsets 1184 ms ok 123 + drop_operator 99 ms ok 124 + password 521 ms ok 125 + identity 2475 ms ok 126 + generated 3794 ms ok 127 + join_hash 3922 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 253 ms ok 129 + brin_multi 746 ms # parallel group (18 tests): async collate.utf8 tidrangescan sysviews dbsize tidscan tid tsrf alter_operator incremental_sort create_role misc_functions misc without_overlaps alter_generic create_table_like collate.icu.utf8 merge ok 130 + create_table_like 878 ms ok 131 + alter_generic 621 ms ok 132 + alter_operator 252 ms ok 133 + misc 422 ms ok 134 + async 98 ms ok 135 + dbsize 172 ms ok 136 + merge 1254 ms ok 137 + misc_functions 394 ms ok 138 + sysviews 170 ms ok 139 + tsrf 251 ms ok 140 + tid 218 ms ok 141 + tidscan 205 ms ok 142 + tidrangescan 169 ms ok 143 + collate.utf8 149 ms ok 144 + collate.icu.utf8 1114 ms ok 145 + incremental_sort 377 ms ok 146 + create_role 389 ms ok 147 + without_overlaps 576 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 2014 ms ok 149 + psql 1865 ms ok 150 + psql_crosstab 156 ms ok 151 + amutils 102 ms ok 152 + stats_ext 3762 ms ok 153 + collate.linux.utf8 16 ms ok 154 + collate.windows.win1252 48 ms ok 155 - select_parallel 2402 ms ok 156 - write_parallel 165 ms ok 157 - vacuum_parallel 101 ms # parallel group (2 tests): subscription publication ok 158 + publication 1225 ms ok 159 + subscription 120 ms # parallel group (17 tests): xmlmap portals_p2 advisory_lock functional_deps select_views combocid bitmapops tsdicts dependency indirect_toast equivclass guc window cluster tsearch foreign_data foreign_key ok 160 + select_views 374 ms ok 161 + portals_p2 221 ms ok 162 + foreign_key 7456 ms ok 163 + cluster 1224 ms ok 164 + dependency 480 ms ok 165 + guc 574 ms ok 166 + bitmapops 411 ms ok 167 + combocid 384 ms ok 168 + tsearch 1582 ms ok 169 + tsdicts 459 ms ok 170 + foreign_data 2611 ms ok 171 + window 949 ms ok 172 + xmlmap 193 ms ok 173 + functional_deps 268 ms ok 174 + advisory_lock 262 ms ok 175 + indirect_toast 481 ms ok 176 + equivclass 491 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 177 + json 313 ms ok 178 + jsonb 595 ms ok 179 + json_encoding 61 ms ok 180 + jsonpath 173 ms ok 181 + jsonpath_encoding 28 ms ok 182 + jsonb_jsonpath 416 ms ok 183 + sqljson 220 ms # parallel group (19 tests): prepare limit returning conversion plancache temp sequence truncate copy2 rowtypes with xml polymorphism rangefuncs largeobject domain session_variables plpgsql alter_table ok 184 + plancache 469 ms ok 185 + limit 278 ms ok 186 + plpgsql 2394 ms ok 187 + copy2 1007 ms ok 188 + temp 729 ms ok 189 + domain 1417 ms ok 190 + rangefuncs 1336 ms ok 191 + prepare 181 ms ok 192 + conversion 307 ms ok 193 + truncate 999 ms ok 194 + alter_table 10708 ms ok 195 + sequence 888 ms ok 196 + polymorphism 1320 ms ok 197 + rowtypes 1039 ms ok 198 + returning 302 ms ok 199 + largeobject 1365 ms ok 200 + with 1104 ms ok 201 + xml 1257 ms not ok 202 + session_variables 1456 ms # parallel group (13 tests): hash_part partition_info memoize explain predicate compression reloptions stats partition_aggregate tuplesort partition_join partition_prune indexing ok 203 + partition_join 3306 ms ok 204 + partition_prune 3699 ms ok 205 + reloptions 405 ms ok 206 + hash_part 121 ms ok 207 + indexing 4024 ms ok 208 + partition_aggregate 1462 ms ok 209 + partition_info 244 ms ok 210 + tuplesort 2047 ms ok 211 + explain 274 ms ok 212 + compression 404 ms ok 213 + memoize 274 ms ok 214 + stats 1202 ms ok 215 + predicate 403 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 344 ms ok 217 + event_trigger 547 ms ok 218 - event_trigger_login 29 ms ok 219 - fast_default 637 ms ok 220 - tablespace 1336 ms 1..220 # 1 of 220 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/session_variables.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/session_variables.out --- /tmp/cirrus-ci-build/src/test/regress/expected/session_variables.out 2024-03-20 08:04:03.788576000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/session_variables.out 2024-03-20 08:06:31.214742000 +0000 @@ -1230,7 +1230,7 @@ ---------------------------------------------- SET SESSION VARIABLE Result - InitPlan 1 (returns $0) + InitPlan 1 -> Aggregate -> Seq Scan on var_tab_test_table (5 rows) @@ -1247,7 +1247,7 @@ ----------------------------------------------------------------------- SET SESSION VARIABLE Result (actual rows=1 loops=1) - InitPlan 1 (returns $0) + InitPlan 1 -> Aggregate (actual rows=1 loops=1) -> Seq Scan on var_tab_test_table (actual rows=10 loops=1) (5 rows) @@ -1267,7 +1267,7 @@ ---------------------------------------------- SET SESSION VARIABLE Result - InitPlan 1 (returns $0) + InitPlan 1 -> Aggregate -> Seq Scan on var_tab_test_table (5 rows) @@ -1284,7 +1284,7 @@ ----------------------------------------------------------------------- SET SESSION VARIABLE Result (actual rows=1 loops=1) - InitPlan 1 (returns $0) + InitPlan 1 -> Aggregate (actual rows=1 loops=1) -> Seq Scan on var_tab_test_table (actual rows=10 loops=1) (5 rows) === EOF === [08:06:47.213](56.956s) not ok 5 - regression tests pass [08:06:47.213](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [08:06:47.213](0.000s) # got: '256' # expected: '0' # Checking port 50715 # Found port 50715 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=50715 host=/tmp/40eChDb3DU Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [08:06:47.216](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: locale 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=50714 host=/tmp/40eChDb3DU dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_rvk1/dump1.sql [08:06:51.476](4.260s) 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/40eChDb3DU -p 50714 -P 50715 --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 [08:06:51.660](0.185s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [08:06:51.662](0.002s) 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/40eChDb3DU -p 50714 -P 50715 --link --check [08:06:52.245](0.583s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [08:06:52.246](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [08:06:52.246](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 20603 ### 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/40eChDb3DU -p 50714 -P 50715 --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 contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage 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* [08:06:54.166](1.920s) ok 12 - run of pg_upgrade --check for new instance [08:06:54.168](0.002s) 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/40eChDb3DU -p 50714 -P 50715 --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 contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage 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 [08:07:13.266](19.098s) ok 14 - run of pg_upgrade for new instance [08:07:13.266](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 23986 [08:07:13.388](0.123s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=50715 host=/tmp/40eChDb3DU dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_rvk1/dump2.sql [08:07:15.583](2.195s) ok 17 - dump after running pg_upgrade [08:07:15.664](0.081s) ok 18 - old and new dumps match after pg_upgrade [08:07:15.665](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" [08:07:15.773](0.108s) # Looks like you failed 1 test of 18.