[17:55:18.554](0.031s) # testing using transfer mode --link # Checking port 60874 # Found port 60874 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=60874 host=/tmp/IrKeJKBCaj Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [17:55:18.609](0.055s) # 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 6121 [17:55:21.008](2.399s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [17:55:21.043](0.035s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [17:55:21.084](0.042s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [17:55:21.117](0.033s) ok 4 - created database with ASCII characters from 91 to 127 [17:55:21.118](0.000s) # running regression tests in old instance # using postmaster on /tmp/IrKeJKBCaj, port 60874 ok 1 - test_setup 475 ms # parallel group (20 tests): varchar char pg_lsn name txid oid uuid float4 regproc text int2 money boolean int4 bit int8 enum float8 numeric rangetypes ok 2 + boolean 319 ms ok 3 + char 179 ms ok 4 + name 182 ms ok 5 + varchar 130 ms ok 6 + text 282 ms ok 7 + int2 294 ms ok 8 + int4 331 ms ok 9 + int8 420 ms ok 10 + oid 224 ms ok 11 + float4 276 ms ok 12 + float8 452 ms ok 13 + bit 408 ms ok 14 + numeric 1087 ms ok 15 + txid 197 ms ok 16 + uuid 229 ms ok 17 + enum 430 ms ok 18 + money 311 ms ok 19 + rangetypes 1087 ms ok 20 + pg_lsn 177 ms ok 21 + regproc 279 ms # parallel group (20 tests): md5 lseg path macaddr circle line point time timetz numerology macaddr8 inet polygon box date timestamp interval timestamptz strings multirangetypes ok 22 + strings 791 ms ok 23 + md5 60 ms ok 24 + numerology 275 ms ok 25 + point 162 ms ok 26 + lseg 101 ms ok 27 + line 120 ms ok 28 + box 471 ms ok 29 + path 107 ms ok 30 + polygon 420 ms ok 31 + circle 117 ms ok 32 + date 524 ms ok 33 + time 182 ms ok 34 + timetz 200 ms ok 35 + timestamp 594 ms ok 36 + timestamptz 737 ms ok 37 + interval 656 ms ok 38 + inet 391 ms ok 39 + macaddr 108 ms ok 40 + macaddr8 361 ms ok 41 + multirangetypes 984 ms # parallel group (12 tests): misc_sanity comments mvcc unicode type_sanity xid tstypes expressions geometry horology regex opr_sanity ok 42 + geometry 321 ms ok 43 + horology 363 ms ok 44 + tstypes 292 ms ok 45 + regex 462 ms ok 46 + type_sanity 189 ms ok 47 + opr_sanity 537 ms ok 48 + misc_sanity 42 ms ok 49 + comments 56 ms ok 50 + expressions 293 ms ok 51 + unicode 106 ms ok 52 + xid 215 ms ok 53 + mvcc 97 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 342 ms ok 55 + copyselect 84 ms ok 56 + copydml 92 ms ok 57 + insert 1113 ms ok 58 + insert_conflict 670 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 18 ms ok 60 + create_misc 108 ms ok 61 + create_operator 101 ms ok 62 + create_procedure 131 ms ok 63 + create_table 1702 ms ok 64 + create_type 125 ms ok 65 + create_schema 98 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2051 ms ok 67 + create_index_spgist 1174 ms ok 68 + create_view 1304 ms ok 69 + index_including 751 ms ok 70 + index_including_gist 575 ms # parallel group (16 tests): create_cast errors hash_func roleattributes create_aggregate drop_if_exists select typed_table infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 264 ms ok 72 + create_function_sql 427 ms ok 73 + create_cast 100 ms ok 74 + constraints 1744 ms ok 75 + triggers 4755 ms ok 76 + select 319 ms ok 77 + inherit 4229 ms ok 78 + typed_table 360 ms ok 79 + vacuum 1002 ms ok 80 + drop_if_exists 283 ms ok 81 + updatable_views 2797 ms ok 82 + roleattributes 216 ms ok 83 + create_am 510 ms ok 84 + hash_func 176 ms ok 85 + errors 141 ms ok 86 + infinite_recurse 414 ms ok 87 - sanity_check 140 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit case random namespace select_into prepared_xacts select_distinct union portals subselect hash_index arrays transactions update join btree_index aggregates ok 88 + select_into 882 ms ok 89 + select_distinct 909 ms ok 90 + select_distinct_on 135 ms ok 91 + select_implicit 498 ms ok 92 + select_having 373 ms ok 93 + subselect 2002 ms ok 94 + union 1627 ms ok 95 + case 639 ms ok 96 + join 3007 ms ok 97 + aggregates 3263 ms ok 98 + transactions 2401 ms ok 99 + random 675 ms ok 100 + portals 1902 ms ok 101 + arrays 2318 ms ok 102 + btree_index 3079 ms ok 103 + hash_index 2174 ms ok 104 + update 2688 ms ok 105 + delete 214 ms ok 106 + namespace 752 ms ok 107 + prepared_xacts 906 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock spgist object_address groupingsets collate replica_identity gist gin matview identity generated brin join_hash privileges rowsecurity ok 108 + brin 3632 ms ok 109 + gin 1888 ms ok 110 + gist 1733 ms ok 111 + spgist 1028 ms ok 112 + privileges 4602 ms ok 113 + init_privs 282 ms ok 114 + security_label 639 ms ok 115 + collate 1392 ms ok 116 + matview 2234 ms ok 117 + lock 983 ms ok 118 + replica_identity 1457 ms ok 119 + rowsecurity 4908 ms ok 120 + object_address 1315 ms ok 121 + tablesample 676 ms ok 122 + groupingsets 1317 ms ok 123 + drop_operator 286 ms ok 124 + password 787 ms ok 125 + identity 2357 ms ok 126 + generated 3299 ms ok 127 + join_hash 3684 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 133 ms ok 129 + brin_multi 974 ms # parallel group (18 tests): dbsize async collate.utf8 tidscan sysviews tidrangescan tsrf misc tid alter_operator create_role incremental_sort misc_functions alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 1493 ms ok 131 + alter_generic 1030 ms ok 132 + alter_operator 504 ms ok 133 + misc 441 ms ok 134 + async 206 ms ok 135 + dbsize 126 ms ok 136 + merge 1638 ms ok 137 + misc_functions 640 ms ok 138 + sysviews 320 ms ok 139 + tsrf 351 ms ok 140 + tid 448 ms ok 141 + tidscan 301 ms ok 142 + tidrangescan 344 ms ok 143 + collate.utf8 240 ms ok 144 + collate.icu.utf8 1374 ms ok 145 + incremental_sort 623 ms ok 146 + create_role 540 ms ok 147 + without_overlaps 2228 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1050 ms ok 149 + psql 1651 ms ok 150 + psql_crosstab 147 ms ok 151 + amutils 47 ms ok 152 + stats_ext 3550 ms ok 153 + collate.linux.utf8 25 ms ok 154 + collate.windows.win1252 18 ms ok 155 - select_parallel 1250 ms ok 156 - write_parallel 97 ms ok 157 - vacuum_parallel 104 ms # parallel group (2 tests): subscription publication ok 158 + publication 2677 ms ok 159 + subscription 184 ms # parallel group (17 tests): advisory_lock portals_p2 xmlmap combocid bitmapops functional_deps select_views dependency equivclass indirect_toast guc tsdicts cluster window tsearch foreign_data foreign_key ok 160 + select_views 580 ms ok 161 + portals_p2 321 ms ok 162 + foreign_key 7306 ms ok 163 + cluster 1093 ms ok 164 + dependency 594 ms ok 165 + guc 684 ms ok 166 + bitmapops 546 ms ok 167 + combocid 452 ms ok 168 + tsearch 1537 ms ok 169 + tsdicts 690 ms ok 170 + foreign_data 2529 ms ok 171 + window 1168 ms ok 172 + xmlmap 354 ms ok 173 + functional_deps 562 ms ok 174 + advisory_lock 313 ms ok 175 + indirect_toast 607 ms ok 176 + equivclass 596 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 463 ms ok 178 + jsonb 791 ms ok 179 + json_encoding 101 ms ok 180 + jsonpath 280 ms ok 181 + jsonpath_encoding 36 ms ok 182 + jsonb_jsonpath 562 ms ok 183 + sqljson 351 ms ok 184 + sqljson_queryfuncs 427 ms ok 185 + sqljson_jsontable 232 ms # parallel group (18 tests): prepare limit conversion returning plancache temp rowtypes truncate with copy2 sequence largeobject xml rangefuncs polymorphism domain plpgsql alter_table ok 186 + plancache 534 ms ok 187 + limit 372 ms ok 188 + plpgsql 2824 ms ok 189 + copy2 1116 ms ok 190 + temp 684 ms ok 191 + domain 1562 ms ok 192 + rangefuncs 1248 ms ok 193 + prepare 233 ms ok 194 + conversion 373 ms ok 195 + truncate 995 ms not ok 196 + alter_table 11542 ms ok 197 + sequence 1125 ms ok 198 + polymorphism 1291 ms ok 199 + rowtypes 917 ms ok 200 + returning 426 ms ok 201 + largeobject 1141 ms ok 202 + with 1084 ms ok 203 + xml 1148 ms # parallel group (15 tests): hash_part predicate reloptions partition_info compression memoize explain partition_merge partition_split partition_aggregate stats tuplesort partition_join indexing partition_prune ok 204 + partition_merge 889 ms ok 205 + partition_split 1011 ms ok 206 + partition_join 4516 ms ok 207 + partition_prune 5146 ms ok 208 + reloptions 365 ms ok 209 + hash_part 145 ms ok 210 + indexing 5011 ms ok 211 + partition_aggregate 1651 ms ok 212 + partition_info 398 ms ok 213 + tuplesort 2066 ms ok 214 + explain 802 ms ok 215 + compression 674 ms ok 216 + memoize 726 ms ok 217 + stats 1802 ms ok 218 + predicate 363 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 465 ms ok 220 + event_trigger 508 ms ok 221 - event_trigger_login 32 ms ok 222 - fast_default 528 ms ok 223 - tablespace 1542 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-16 17:54:36.935498000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-16 17:56:13.376804000 +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 +-------+------------+---------------+-------------+---------------------- + 37641 | | 0 | 37641 | pktable + 37652 | | 0 | 37652 | fktable + 37646 | | 0 | 37646 | pktable_pkey + 38282 | | 0 | 38287 | foo + 38292 | | 0 | 38292 | pg_toast_38282_index + 38291 | | 0 | 38291 | pg_toast_38282 + 38564 | | 0 | 38564 | old_oids + 38583 | | 0 | 38583 | pg_toast_38580 + 38584 | | 0 | 38584 | pg_toast_38580_index + 38580 | | 0 | 38580 | recur2 + 38575 | | 0 | 38575 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [17:56:21.203](60.085s) not ok 5 - regression tests pass [17:56:21.203](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [17:56:21.203](0.000s) # got: '256' # expected: '0' # Checking port 60875 # Found port 60875 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=60875 host=/tmp/IrKeJKBCaj Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [17:56:21.207](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=60874 host=/tmp/IrKeJKBCaj dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_tHee/dump1.sql [17:56:26.003](4.796s) 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/IrKeJKBCaj -p 60874 -P 60875 --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 [17:56:26.145](0.142s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [17:56:26.145](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/IrKeJKBCaj -p 60874 -P 60875 --link --check [17:56:26.774](0.628s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [17:56:26.776](0.003s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [17:56:26.779](0.003s) 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 18683 ### 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/IrKeJKBCaj -p 60874 -P 60875 --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* [17:56:28.837](2.059s) ok 12 - run of pg_upgrade --check for new instance [17:56:28.837](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/IrKeJKBCaj -p 60874 -P 60875 --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 [17:56:50.118](21.280s) ok 14 - run of pg_upgrade for new instance [17:56:50.118](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 22648 [17:56:50.240](0.122s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=60875 host=/tmp/IrKeJKBCaj dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_tHee/dump2.sql [17:56:52.418](2.178s) ok 17 - dump after running pg_upgrade [17:56:52.498](0.080s) ok 18 - old and new dumps match after pg_upgrade [17:56:52.498](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" [17:56:52.607](0.109s) # Looks like you failed 1 test of 18.