[19:37:53.371](0.025s) # testing using transfer mode --link # Checking port 53603 # Found port 53603 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=53603 host=/tmp/Fk_AARf_rh Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [19:37:53.379](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 --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 6046 [19:37:55.300](1.921s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [19:37:55.343](0.042s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [19:37:55.376](0.033s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [19:37:55.402](0.027s) ok 4 - created database with ASCII characters from 91 to 127 [19:37:55.403](0.001s) # running regression tests in old instance # using postmaster on /tmp/Fk_AARf_rh, port 53603 ok 1 - test_setup 573 ms # parallel group (20 tests): varchar pg_lsn char oid txid name uuid int2 text boolean regproc float4 money int4 int8 float8 bit enum rangetypes numeric ok 2 + boolean 244 ms ok 3 + char 117 ms ok 4 + name 162 ms ok 5 + varchar 107 ms ok 6 + text 212 ms ok 7 + int2 195 ms ok 8 + int4 286 ms ok 9 + int8 319 ms ok 10 + oid 128 ms ok 11 + float4 261 ms ok 12 + float8 340 ms ok 13 + bit 353 ms ok 14 + numeric 1037 ms ok 15 + txid 158 ms ok 16 + uuid 189 ms ok 17 + enum 364 ms ok 18 + money 263 ms ok 19 + rangetypes 890 ms ok 20 + pg_lsn 114 ms ok 21 + regproc 255 ms # parallel group (20 tests): md5 circle lseg path time macaddr line point timetz numerology macaddr8 polygon inet date interval box timestamp strings timestamptz multirangetypes ok 22 + strings 724 ms ok 23 + md5 55 ms ok 24 + numerology 250 ms ok 25 + point 138 ms ok 26 + lseg 83 ms ok 27 + line 128 ms ok 28 + box 385 ms ok 29 + path 91 ms ok 30 + polygon 282 ms ok 31 + circle 79 ms ok 32 + date 310 ms ok 33 + time 121 ms ok 34 + timetz 143 ms ok 35 + timestamp 537 ms ok 36 + timestamptz 757 ms ok 37 + interval 375 ms ok 38 + inet 285 ms ok 39 + macaddr 124 ms ok 40 + macaddr8 271 ms ok 41 + multirangetypes 928 ms # parallel group (12 tests): comments misc_sanity mvcc unicode type_sanity xid expressions tstypes regex geometry horology opr_sanity ok 42 + geometry 328 ms ok 43 + horology 386 ms ok 44 + tstypes 267 ms ok 45 + regex 312 ms ok 46 + type_sanity 178 ms ok 47 + opr_sanity 448 ms ok 48 + misc_sanity 40 ms ok 49 + comments 30 ms ok 50 + expressions 249 ms ok 51 + unicode 84 ms ok 52 + xid 218 ms ok 53 + mvcc 75 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 299 ms ok 55 + copyselect 103 ms ok 56 + copydml 118 ms ok 57 + insert 1129 ms ok 58 + insert_conflict 650 ms # parallel group (7 tests): create_function_c create_schema create_operator create_type create_misc create_procedure create_table ok 59 + create_function_c 19 ms ok 60 + create_misc 139 ms ok 61 + create_operator 123 ms ok 62 + create_procedure 144 ms ok 63 + create_table 1608 ms ok 64 + create_type 129 ms ok 65 + create_schema 105 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2255 ms ok 67 + create_index_spgist 1005 ms ok 68 + create_view 1269 ms ok 69 + index_including 728 ms ok 70 + index_including_gist 537 ms # parallel group (16 tests): errors roleattributes create_cast hash_func select create_aggregate typed_table drop_if_exists infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 303 ms ok 72 + create_function_sql 420 ms ok 73 + create_cast 140 ms ok 74 + constraints 1878 ms ok 75 + triggers 6144 ms ok 76 + select 208 ms ok 77 + inherit 5147 ms ok 78 + typed_table 333 ms ok 79 + vacuum 988 ms ok 80 + drop_if_exists 342 ms ok 81 + updatable_views 3210 ms ok 82 + roleattributes 138 ms ok 83 + create_am 460 ms ok 84 + hash_func 160 ms ok 85 + errors 106 ms ok 86 + infinite_recurse 391 ms ok 87 - sanity_check 96 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit case namespace select_into prepared_xacts select_distinct transactions portals union subselect hash_index arrays update aggregates btree_index join ok 88 + select_into 315 ms ok 89 + select_distinct 414 ms ok 90 + select_distinct_on 70 ms ok 91 + select_implicit 213 ms ok 92 + select_having 120 ms ok 93 + subselect 880 ms ok 94 + union 786 ms ok 95 + case 232 ms ok 96 + join 1903 ms ok 97 + aggregates 1469 ms ok 98 + transactions 745 ms ok 99 + random 211 ms ok 100 + portals 762 ms ok 101 + arrays 989 ms ok 102 + btree_index 1805 ms ok 103 + hash_index 911 ms ok 104 + update 1374 ms ok 105 + delete 113 ms ok 106 + namespace 283 ms ok 107 + prepared_xacts 328 ms # parallel group (20 tests): init_privs drop_operator security_label password tablesample object_address lock spgist collate groupingsets replica_identity gin gist matview identity brin join_hash generated privileges rowsecurity ok 108 + brin 3761 ms ok 109 + gin 1706 ms ok 110 + gist 1914 ms ok 111 + spgist 1230 ms ok 112 + privileges 4553 ms ok 113 + init_privs 93 ms ok 114 + security_label 370 ms ok 115 + collate 1230 ms ok 116 + matview 2696 ms ok 117 + lock 1096 ms ok 118 + replica_identity 1613 ms ok 119 + rowsecurity 4660 ms ok 120 + object_address 975 ms ok 121 + tablesample 805 ms ok 122 + groupingsets 1234 ms ok 123 + drop_operator 280 ms ok 124 + password 435 ms ok 125 + identity 2951 ms ok 126 + generated 4070 ms ok 127 + join_hash 3814 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 208 ms ok 129 + brin_multi 676 ms # parallel group (18 tests): async dbsize tidscan tid tidrangescan alter_operator sysviews collate.utf8 misc_functions misc tsrf incremental_sort create_role alter_generic create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 1250 ms ok 131 + alter_generic 685 ms ok 132 + alter_operator 270 ms ok 133 + misc 389 ms ok 134 + async 71 ms ok 135 + dbsize 140 ms ok 136 + merge 1286 ms ok 137 + misc_functions 359 ms ok 138 + sysviews 315 ms ok 139 + tsrf 388 ms ok 140 + tid 263 ms ok 141 + tidscan 188 ms ok 142 + tidrangescan 268 ms ok 143 + collate.utf8 320 ms ok 144 + collate.icu.utf8 1264 ms ok 145 + incremental_sort 444 ms ok 146 + create_role 464 ms ok 147 + without_overlaps 1778 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 2052 ms ok 149 + psql 1865 ms ok 150 + psql_crosstab 104 ms ok 151 + amutils 85 ms ok 152 + stats_ext 3796 ms ok 153 + collate.linux.utf8 26 ms ok 154 + collate.windows.win1252 17 ms ok 155 - select_parallel 1997 ms ok 156 - write_parallel 106 ms ok 157 - vacuum_parallel 99 ms # parallel group (2 tests): subscription publication ok 158 + publication 915 ms ok 159 + subscription 141 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap combocid functional_deps bitmapops equivclass indirect_toast tsdicts guc select_views dependency tsearch window cluster foreign_data foreign_key ok 160 + select_views 555 ms ok 161 + portals_p2 158 ms ok 162 + foreign_key 7665 ms ok 163 + cluster 1475 ms ok 164 + dependency 615 ms ok 165 + guc 521 ms ok 166 + bitmapops 453 ms ok 167 + combocid 241 ms ok 168 + tsearch 979 ms ok 169 + tsdicts 499 ms ok 170 + foreign_data 3039 ms ok 171 + window 989 ms ok 172 + xmlmap 177 ms ok 173 + functional_deps 294 ms ok 174 + advisory_lock 162 ms ok 175 + indirect_toast 478 ms ok 176 + equivclass 471 ms # parallel group (9 tests): json_encoding jsonpath_encoding jsonpath sqljson_jsontable sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 400 ms ok 178 + jsonb 756 ms ok 179 + json_encoding 55 ms ok 180 + jsonpath 166 ms ok 181 + jsonpath_encoding 71 ms ok 182 + jsonb_jsonpath 604 ms ok 183 + sqljson 214 ms ok 184 + sqljson_queryfuncs 361 ms ok 185 + sqljson_jsontable 173 ms # parallel group (18 tests): prepare limit conversion returning plancache temp rowtypes sequence copy2 xml with truncate largeobject polymorphism rangefuncs domain plpgsql alter_table ok 186 + plancache 535 ms ok 187 + limit 317 ms ok 188 + plpgsql 2408 ms ok 189 + copy2 1065 ms ok 190 + temp 598 ms ok 191 + domain 1517 ms ok 192 + rangefuncs 1353 ms ok 193 + prepare 150 ms ok 194 + conversion 321 ms ok 195 + truncate 1139 ms not ok 196 + alter_table 12924 ms ok 197 + sequence 1062 ms ok 198 + polymorphism 1261 ms ok 199 + rowtypes 724 ms ok 200 + returning 368 ms ok 201 + largeobject 1177 ms ok 202 + with 1120 ms ok 203 + xml 1069 ms # parallel group (15 tests): hash_part reloptions predicate partition_info explain memoize compression partition_merge partition_aggregate stats tuplesort partition_split partition_prune partition_join indexing ok 204 + partition_merge 1326 ms ok 205 + partition_split 2078 ms ok 206 + partition_join 4556 ms ok 207 + partition_prune 4322 ms ok 208 + reloptions 112 ms ok 209 + hash_part 69 ms ok 210 + indexing 4875 ms ok 211 + partition_aggregate 1660 ms ok 212 + partition_info 198 ms ok 213 + tuplesort 2031 ms ok 214 + explain 687 ms ok 215 + compression 1317 ms ok 216 + memoize 1056 ms ok 217 + stats 1908 ms ok 218 + predicate 116 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 420 ms ok 220 + event_trigger 464 ms ok 221 - event_trigger_login 65 ms ok 222 - fast_default 551 ms ok 223 - tablespace 1362 ms 1..223 # 1 of 223 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/alter_table.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out --- /tmp/cirrus-ci-build/src/test/regress/expected/alter_table.out 2024-04-23 19:37:11.467532000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-23 19:38:47.660282000 +0000 @@ -3476,9 +3476,20 @@ WHERE relkind IN ('r', 'i', 'S', 't', 'm') AND mapped_oid IS DISTINCT FROM oid; SELECT m.* FROM filenode_mapping m LEFT JOIN pg_class c ON c.oid = m.oid WHERE c.oid IS NOT NULL OR m.mapped_oid IS NOT NULL; - oid | mapped_oid | reltablespace | relfilenode | relname ------+------------+---------------+-------------+--------- -(0 rows) + oid | mapped_oid | reltablespace | relfilenode | relname +-------+------------+---------------+-------------+---------------------- + 37876 | | 0 | 37876 | pktable_pkey + 37872 | | 0 | 37872 | pktable + 37878 | | 0 | 37878 | fktable + 38436 | | 0 | 38441 | foo + 38445 | | 0 | 38445 | pg_toast_38436_index + 38444 | | 0 | 38444 | pg_toast_38436 + 38668 | | 0 | 38668 | old_oids + 38685 | | 0 | 38685 | pg_toast_38682 + 38686 | | 0 | 38686 | pg_toast_38682_index + 38682 | | 0 | 38682 | recur2 + 38677 | | 0 | 38677 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [19:38:55.085](59.682s) not ok 5 - regression tests pass [19:38:55.085](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [19:38:55.085](0.000s) # got: '256' # expected: '0' # Checking port 53604 # Found port 53604 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=53604 host=/tmp/Fk_AARf_rh Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [19:38:55.088](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=53603 host=/tmp/Fk_AARf_rh dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_nWvn/dump1.sql [19:38:58.964](3.875s) 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/Fk_AARf_rh -p 53603 -P 53604 --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:38:59.146](0.182s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [19:38:59.147](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/Fk_AARf_rh -p 53603 -P 53604 --link --check [19:39:00.272](1.125s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [19:39:00.273](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [19:39:00.273](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 18973 ### 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/Fk_AARf_rh -p 53603 -P 53604 --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* [19:39:02.944](2.671s) ok 12 - run of pg_upgrade --check for new instance [19:39:02.945](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/Fk_AARf_rh -p 53603 -P 53604 --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 [19:39:20.584](17.639s) ok 14 - run of pg_upgrade for new instance [19:39:20.584](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 22651 [19:39:20.719](0.135s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=53604 host=/tmp/Fk_AARf_rh dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_nWvn/dump2.sql [19:39:22.852](2.133s) ok 17 - dump after running pg_upgrade [19:39:22.933](0.081s) ok 18 - old and new dumps match after pg_upgrade [19:39:22.934](0.001s) 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:39:23.041](0.107s) # Looks like you failed 1 test of 18.