[03:32:47.819](0.018s) # testing using transfer mode --link # Checking port 60247 # Found port 60247 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=60247 host=/tmp/ETXLtHeLZO Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [03:32:47.822](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_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 7733 [03:32:50.132](2.310s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [03:32:50.189](0.058s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [03:32:50.253](0.063s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [03:32:50.355](0.102s) ok 4 - created database with ASCII characters from 91 to 127 [03:32:50.357](0.002s) # running regression tests in old instance # using postmaster on /tmp/ETXLtHeLZO, port 60247 ok 1 - test_setup 413 ms # parallel group (20 tests): varchar char pg_lsn txid oid name uuid text money regproc int2 int4 boolean float4 bit float8 int8 enum rangetypes numeric ok 2 + boolean 297 ms ok 3 + char 135 ms ok 4 + name 197 ms ok 5 + varchar 109 ms ok 6 + text 243 ms ok 7 + int2 278 ms ok 8 + int4 286 ms ok 9 + int8 365 ms ok 10 + oid 192 ms ok 11 + float4 301 ms ok 12 + float8 352 ms ok 13 + bit 348 ms ok 14 + numeric 983 ms ok 15 + txid 178 ms ok 16 + uuid 207 ms ok 17 + enum 372 ms ok 18 + money 273 ms ok 19 + rangetypes 797 ms ok 20 + pg_lsn 170 ms ok 21 + regproc 276 ms # parallel group (20 tests): md5 path lseg circle macaddr time point line timetz macaddr8 numerology inet polygon box date timestamp strings timestamptz interval multirangetypes ok 22 + strings 695 ms ok 23 + md5 45 ms ok 24 + numerology 288 ms ok 25 + point 136 ms ok 26 + lseg 76 ms ok 27 + line 161 ms ok 28 + box 413 ms ok 29 + path 71 ms ok 30 + polygon 332 ms ok 31 + circle 79 ms ok 32 + date 549 ms ok 33 + time 132 ms ok 34 + timetz 162 ms ok 35 + timestamp 551 ms ok 36 + timestamptz 729 ms ok 37 + interval 738 ms ok 38 + inet 323 ms ok 39 + macaddr 109 ms ok 40 + macaddr8 218 ms ok 41 + multirangetypes 801 ms # parallel group (12 tests): comments misc_sanity unicode mvcc expressions xid type_sanity geometry tstypes horology regex opr_sanity ok 42 + geometry 280 ms ok 43 + horology 390 ms ok 44 + tstypes 349 ms ok 45 + regex 405 ms ok 46 + type_sanity 204 ms ok 47 + opr_sanity 440 ms ok 48 + misc_sanity 40 ms ok 49 + comments 26 ms ok 50 + expressions 165 ms ok 51 + unicode 43 ms ok 52 + xid 197 ms ok 53 + mvcc 64 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 233 ms ok 55 + copyselect 69 ms ok 56 + copydml 208 ms ok 57 + insert 1204 ms ok 58 + insert_conflict 642 ms # parallel group (7 tests): create_function_c create_schema create_operator create_procedure create_misc create_type create_table ok 59 + create_function_c 27 ms ok 60 + create_misc 158 ms ok 61 + create_operator 127 ms ok 62 + create_procedure 143 ms ok 63 + create_table 1542 ms ok 64 + create_type 191 ms ok 65 + create_schema 111 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2313 ms ok 67 + create_index_spgist 1073 ms ok 68 + create_view 1434 ms ok 69 + index_including 788 ms ok 70 + index_including_gist 600 ms # parallel group (16 tests): create_cast hash_func roleattributes create_aggregate errors select typed_table drop_if_exists create_function_sql create_am infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 242 ms ok 72 + create_function_sql 435 ms ok 73 + create_cast 84 ms ok 74 + constraints 1565 ms ok 75 + triggers 5754 ms ok 76 + select 276 ms ok 77 + inherit 4114 ms ok 78 + typed_table 359 ms ok 79 + vacuum 1012 ms ok 80 + drop_if_exists 405 ms ok 81 + updatable_views 3593 ms ok 82 + roleattributes 205 ms ok 83 + create_am 469 ms ok 84 + hash_func 105 ms ok 85 + errors 244 ms ok 86 + infinite_recurse 495 ms ok 87 - sanity_check 155 ms # parallel group (20 tests): select_distinct_on select_having delete namespace case select_implicit random select_distinct select_into prepared_xacts union transactions portals hash_index arrays subselect update btree_index aggregates join ok 88 + select_into 400 ms ok 89 + select_distinct 306 ms ok 90 + select_distinct_on 87 ms ok 91 + select_implicit 260 ms ok 92 + select_having 125 ms ok 93 + subselect 1193 ms ok 94 + union 691 ms ok 95 + case 254 ms ok 96 + join 2182 ms ok 97 + aggregates 2091 ms ok 98 + transactions 813 ms ok 99 + random 276 ms ok 100 + portals 830 ms ok 101 + arrays 1104 ms ok 102 + btree_index 2031 ms ok 103 + hash_index 1000 ms ok 104 + update 1635 ms ok 105 + delete 132 ms ok 106 + namespace 235 ms ok 107 + prepared_xacts 429 ms # parallel group (20 tests): init_privs drop_operator password tablesample security_label lock object_address groupingsets collate replica_identity spgist gin gist brin matview identity generated join_hash privileges rowsecurity ok 108 + brin 2041 ms ok 109 + gin 1525 ms ok 110 + gist 1541 ms ok 111 + spgist 1428 ms ok 112 + privileges 4497 ms ok 113 + init_privs 55 ms ok 114 + security_label 532 ms ok 115 + collate 1275 ms ok 116 + matview 2327 ms ok 117 + lock 947 ms ok 118 + replica_identity 1348 ms ok 119 + rowsecurity 4658 ms ok 120 + object_address 956 ms ok 121 + tablesample 386 ms ok 122 + groupingsets 1217 ms ok 123 + drop_operator 140 ms ok 124 + password 255 ms ok 125 + identity 2428 ms ok 126 + generated 3737 ms ok 127 + join_hash 4127 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 196 ms ok 129 + brin_multi 948 ms # parallel group (18 tests): async collate.utf8 dbsize sysviews tid tsrf tidrangescan tidscan alter_operator misc incremental_sort misc_functions create_role alter_generic merge collate.icu.utf8 create_table_like without_overlaps ok 130 + create_table_like 1437 ms ok 131 + alter_generic 632 ms ok 132 + alter_operator 263 ms ok 133 + misc 344 ms ok 134 + async 64 ms ok 135 + dbsize 159 ms ok 136 + merge 1150 ms ok 137 + misc_functions 392 ms ok 138 + sysviews 171 ms ok 139 + tsrf 203 ms ok 140 + tid 194 ms ok 141 + tidscan 237 ms ok 142 + tidrangescan 213 ms ok 143 + collate.utf8 139 ms ok 144 + collate.icu.utf8 1247 ms ok 145 + incremental_sort 384 ms ok 146 + create_role 452 ms ok 147 + without_overlaps 1717 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1518 ms ok 149 + psql 1470 ms ok 150 + psql_crosstab 123 ms ok 151 + amutils 44 ms ok 152 + stats_ext 3727 ms ok 153 + collate.linux.utf8 29 ms ok 154 + collate.windows.win1252 29 ms ok 155 - select_parallel 1197 ms ok 156 - write_parallel 170 ms ok 157 - vacuum_parallel 141 ms # parallel group (2 tests): subscription publication ok 158 + publication 1550 ms ok 159 + subscription 593 ms # parallel group (17 tests): portals_p2 advisory_lock functional_deps xmlmap combocid bitmapops select_views indirect_toast equivclass dependency tsdicts guc window tsearch cluster foreign_data foreign_key ok 160 + select_views 567 ms ok 161 + portals_p2 257 ms ok 162 + foreign_key 8000 ms ok 163 + cluster 1814 ms ok 164 + dependency 686 ms ok 165 + guc 1011 ms ok 166 + bitmapops 503 ms ok 167 + combocid 475 ms ok 168 + tsearch 1676 ms ok 169 + tsdicts 744 ms ok 170 + foreign_data 3840 ms ok 171 + window 1383 ms ok 172 + xmlmap 460 ms ok 173 + functional_deps 379 ms ok 174 + advisory_lock 379 ms ok 175 + indirect_toast 609 ms ok 176 + equivclass 663 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson json sqljson_queryfuncs jsonb_jsonpath jsonb ok 177 + json 317 ms ok 178 + jsonb 570 ms ok 179 + json_encoding 98 ms ok 180 + jsonpath 202 ms ok 181 + jsonpath_encoding 29 ms ok 182 + jsonb_jsonpath 465 ms ok 183 + sqljson 227 ms ok 184 + sqljson_queryfuncs 326 ms ok 185 + sqljson_jsontable 126 ms # parallel group (18 tests): prepare returning conversion limit plancache temp truncate copy2 with rowtypes sequence xml polymorphism largeobject rangefuncs domain plpgsql alter_table ok 186 + plancache 487 ms ok 187 + limit 432 ms ok 188 + plpgsql 2731 ms ok 189 + copy2 1062 ms ok 190 + temp 623 ms ok 191 + domain 1508 ms ok 192 + rangefuncs 1426 ms ok 193 + prepare 189 ms ok 194 + conversion 374 ms ok 195 + truncate 1026 ms not ok 196 + alter_table 11188 ms ok 197 + sequence 1141 ms ok 198 + polymorphism 1220 ms ok 199 + rowtypes 1136 ms ok 200 + returning 304 ms ok 201 + largeobject 1257 ms ok 202 + with 1109 ms ok 203 + xml 1192 ms # parallel group (15 tests): predicate hash_part partition_info reloptions explain memoize compression partition_aggregate partition_merge stats tuplesort partition_split partition_prune partition_join indexing ok 204 + partition_merge 1542 ms ok 205 + partition_split 2189 ms ok 206 + partition_join 4395 ms ok 207 + partition_prune 4335 ms ok 208 + reloptions 382 ms ok 209 + hash_part 199 ms ok 210 + indexing 4858 ms ok 211 + partition_aggregate 1536 ms ok 212 + partition_info 268 ms ok 213 + tuplesort 1893 ms ok 214 + explain 499 ms ok 215 + compression 1235 ms ok 216 + memoize 607 ms ok 217 + stats 1802 ms ok 218 + predicate 177 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 538 ms ok 220 + event_trigger 663 ms ok 221 - event_trigger_login 204 ms ok 222 - fast_default 581 ms ok 223 - tablespace 1404 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-07 03:31:18.758656000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-07 03:33:40.638502000 +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 +-------+------------+---------------+-------------+---------------------- + 37734 | | 0 | 37734 | pktable_pkey + 37731 | | 0 | 37731 | pktable + 37736 | | 0 | 37736 | fktable + 38249 | | 0 | 38254 | foo + 38258 | | 0 | 38258 | pg_toast_38249_index + 38257 | | 0 | 38257 | pg_toast_38249 + 38534 | | 0 | 38534 | old_oids + 38567 | | 0 | 38567 | pg_toast_38563 + 38568 | | 0 | 38568 | pg_toast_38563_index + 38563 | | 0 | 38563 | recur2 + 38556 | | 0 | 38556 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [03:33:48.635](58.278s) not ok 5 - regression tests pass [03:33:48.635](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [03:33:48.635](0.000s) # got: '256' # expected: '0' # Checking port 60248 # Found port 60248 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=60248 host=/tmp/ETXLtHeLZO Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [03:33:48.639](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=60247 host=/tmp/ETXLtHeLZO dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_yQ_D/dump1.sql [03:33:53.036](4.397s) 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/ETXLtHeLZO -p 60247 -P 60248 --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 [03:33:53.181](0.145s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [03:33:53.181](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/ETXLtHeLZO -p 60247 -P 60248 --link --check [03:33:53.947](0.766s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [03:33:53.948](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [03:33:53.948](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 20465 ### 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/ETXLtHeLZO -p 60247 -P 60248 --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* [03:33:56.027](2.078s) ok 12 - run of pg_upgrade --check for new instance [03:33:56.027](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/ETXLtHeLZO -p 60247 -P 60248 --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 [03:34:15.850](19.823s) ok 14 - run of pg_upgrade for new instance [03:34:15.850](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 23906 [03:34:15.974](0.125s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=60248 host=/tmp/ETXLtHeLZO dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_yQ_D/dump2.sql [03:34:17.962](1.988s) ok 17 - dump after running pg_upgrade [03:34:18.041](0.079s) ok 18 - old and new dumps match after pg_upgrade [03:34:18.041](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" [03:34:18.152](0.111s) # Looks like you failed 1 test of 18.