[00:09:23.435](0.013s) # testing using transfer mode --link # Checking port 65021 # Found port 65021 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=65021 host=/tmp/RCCq6QbaT4 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [00:09:23.466](0.030s) # 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 6073 [00:09:25.426](1.961s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [00:09:25.479](0.053s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [00:09:25.565](0.085s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [00:09:25.629](0.064s) ok 4 - created database with ASCII characters from 91 to 127 [00:09:25.629](0.000s) # running regression tests in old instance # using postmaster on /tmp/RCCq6QbaT4, port 65021 ok 1 - test_setup 396 ms # parallel group (20 tests): varchar char oid pg_lsn uuid name text regproc int4 money txid float4 int2 bit boolean int8 enum float8 rangetypes numeric ok 2 + boolean 497 ms ok 3 + char 148 ms ok 4 + name 257 ms ok 5 + varchar 128 ms ok 6 + text 260 ms ok 7 + int2 410 ms ok 8 + int4 392 ms ok 9 + int8 511 ms ok 10 + oid 212 ms ok 11 + float4 407 ms ok 12 + float8 541 ms ok 13 + bit 470 ms ok 14 + numeric 1277 ms ok 15 + txid 404 ms ok 16 + uuid 250 ms ok 17 + enum 540 ms ok 18 + money 395 ms ok 19 + rangetypes 1007 ms ok 20 + pg_lsn 232 ms ok 21 + regproc 378 ms # parallel group (20 tests): md5 path lseg circle line macaddr time timetz point macaddr8 numerology inet polygon date box timestamp interval strings timestamptz multirangetypes ok 22 + strings 591 ms ok 23 + md5 61 ms ok 24 + numerology 244 ms ok 25 + point 157 ms ok 26 + lseg 82 ms ok 27 + line 129 ms ok 28 + box 454 ms ok 29 + path 78 ms ok 30 + polygon 301 ms ok 31 + circle 87 ms ok 32 + date 336 ms ok 33 + time 139 ms ok 34 + timetz 147 ms ok 35 + timestamp 527 ms ok 36 + timestamptz 665 ms ok 37 + interval 551 ms ok 38 + inet 276 ms ok 39 + macaddr 135 ms ok 40 + macaddr8 186 ms ok 41 + multirangetypes 760 ms # parallel group (12 tests): comments unicode misc_sanity mvcc xid expressions type_sanity regex geometry tstypes horology opr_sanity ok 42 + geometry 416 ms ok 43 + horology 472 ms ok 44 + tstypes 448 ms ok 45 + regex 396 ms ok 46 + type_sanity 279 ms ok 47 + opr_sanity 482 ms ok 48 + misc_sanity 103 ms ok 49 + comments 50 ms ok 50 + expressions 257 ms ok 51 + unicode 81 ms ok 52 + xid 231 ms ok 53 + mvcc 161 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 311 ms ok 55 + copyselect 95 ms ok 56 + copydml 95 ms ok 57 + insert 1250 ms ok 58 + insert_conflict 604 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_misc create_procedure create_table ok 59 + create_function_c 50 ms ok 60 + create_misc 231 ms ok 61 + create_operator 154 ms ok 62 + create_procedure 235 ms ok 63 + create_table 916 ms ok 64 + create_type 175 ms ok 65 + create_schema 164 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2803 ms ok 67 + create_index_spgist 1516 ms ok 68 + create_view 1853 ms ok 69 + index_including 1331 ms ok 70 + index_including_gist 782 ms # parallel group (16 tests): hash_func create_cast errors roleattributes create_aggregate typed_table select drop_if_exists infinite_recurse create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 255 ms ok 72 + create_function_sql 550 ms ok 73 + create_cast 210 ms ok 74 + constraints 1655 ms ok 75 + triggers 4554 ms ok 76 + select 346 ms ok 77 + inherit 3617 ms ok 78 + typed_table 309 ms ok 79 + vacuum 1038 ms ok 80 + drop_if_exists 371 ms ok 81 + updatable_views 2442 ms ok 82 + roleattributes 239 ms ok 83 + create_am 540 ms ok 84 + hash_func 165 ms ok 85 + errors 219 ms ok 86 + infinite_recurse 463 ms ok 87 - sanity_check 74 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit random namespace select_distinct case prepared_xacts select_into union hash_index subselect portals transactions arrays update aggregates btree_index join ok 88 + select_into 408 ms ok 89 + select_distinct 314 ms ok 90 + select_distinct_on 91 ms ok 91 + select_implicit 219 ms ok 92 + select_having 155 ms ok 93 + subselect 1615 ms ok 94 + union 965 ms ok 95 + case 318 ms ok 96 + join 3592 ms ok 97 + aggregates 2825 ms ok 98 + transactions 1949 ms ok 99 + random 236 ms ok 100 + portals 1616 ms ok 101 + arrays 2332 ms ok 102 + btree_index 2832 ms ok 103 + hash_index 1415 ms ok 104 + update 2533 ms ok 105 + delete 96 ms ok 106 + namespace 249 ms ok 107 + prepared_xacts 340 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock collate object_address spgist gin groupingsets replica_identity gist identity matview brin join_hash generated rowsecurity privileges ok 108 + brin 4225 ms ok 109 + gin 1131 ms ok 110 + gist 1789 ms ok 111 + spgist 1130 ms ok 112 + privileges 4803 ms ok 113 + init_privs 58 ms ok 114 + security_label 365 ms ok 115 + collate 1076 ms ok 116 + matview 2316 ms ok 117 + lock 837 ms ok 118 + replica_identity 1435 ms ok 119 + rowsecurity 4742 ms ok 120 + object_address 1093 ms ok 121 + tablesample 423 ms ok 122 + groupingsets 1352 ms ok 123 + drop_operator 286 ms ok 124 + password 650 ms ok 125 + identity 2214 ms ok 126 + generated 4359 ms ok 127 + join_hash 4308 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 200 ms ok 129 + brin_multi 1042 ms # parallel group (18 tests): async dbsize sysviews collate.utf8 tidscan tidrangescan tid alter_operator tsrf misc misc_functions incremental_sort create_role alter_generic create_table_like merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 1133 ms ok 131 + alter_generic 890 ms ok 132 + alter_operator 359 ms ok 133 + misc 396 ms ok 134 + async 80 ms ok 135 + dbsize 121 ms ok 136 + merge 1207 ms ok 137 + misc_functions 445 ms ok 138 + sysviews 151 ms ok 139 + tsrf 395 ms ok 140 + tid 276 ms ok 141 + tidscan 206 ms ok 142 + tidrangescan 246 ms ok 143 + collate.utf8 173 ms ok 144 + collate.icu.utf8 1458 ms ok 145 + incremental_sort 476 ms ok 146 + create_role 519 ms ok 147 + without_overlaps 1698 ms # parallel group (7 tests): collate.windows.win1252 amutils collate.linux.utf8 psql_crosstab rules psql stats_ext ok 148 + rules 1304 ms ok 149 + psql 1560 ms ok 150 + psql_crosstab 62 ms ok 151 + amutils 40 ms ok 152 + stats_ext 4027 ms ok 153 + collate.linux.utf8 41 ms ok 154 + collate.windows.win1252 18 ms ok 155 - select_parallel 1241 ms ok 156 - write_parallel 166 ms ok 157 - vacuum_parallel 129 ms # parallel group (2 tests): subscription publication ok 158 + publication 1748 ms ok 159 + subscription 618 ms # parallel group (17 tests): advisory_lock xmlmap portals_p2 functional_deps combocid tsdicts indirect_toast bitmapops dependency equivclass select_views guc tsearch cluster window foreign_data foreign_key ok 160 + select_views 723 ms ok 161 + portals_p2 313 ms ok 162 + foreign_key 7695 ms ok 163 + cluster 1286 ms ok 164 + dependency 631 ms ok 165 + guc 830 ms ok 166 + bitmapops 619 ms ok 167 + combocid 418 ms ok 168 + tsearch 1263 ms ok 169 + tsdicts 587 ms ok 170 + foreign_data 3214 ms ok 171 + window 1696 ms ok 172 + xmlmap 252 ms ok 173 + functional_deps 411 ms ok 174 + advisory_lock 242 ms ok 175 + indirect_toast 617 ms ok 176 + equivclass 709 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 428 ms ok 178 + jsonb 884 ms ok 179 + json_encoding 99 ms ok 180 + jsonpath 214 ms ok 181 + jsonpath_encoding 76 ms ok 182 + jsonb_jsonpath 540 ms ok 183 + sqljson 222 ms ok 184 + sqljson_queryfuncs 377 ms ok 185 + sqljson_jsontable 191 ms # parallel group (18 tests): prepare conversion returning limit plancache temp rowtypes with truncate sequence largeobject xml copy2 polymorphism rangefuncs domain plpgsql alter_table ok 186 + plancache 517 ms ok 187 + limit 349 ms ok 188 + plpgsql 2691 ms ok 189 + copy2 1179 ms ok 190 + temp 728 ms ok 191 + domain 1454 ms ok 192 + rangefuncs 1289 ms ok 193 + prepare 228 ms ok 194 + conversion 310 ms ok 195 + truncate 1115 ms not ok 196 + alter_table 11933 ms ok 197 + sequence 1141 ms ok 198 + polymorphism 1186 ms ok 199 + rowtypes 828 ms ok 200 + returning 346 ms ok 201 + largeobject 1146 ms ok 202 + with 907 ms ok 203 + xml 1167 ms # parallel group (15 tests): predicate memoize explain reloptions hash_part partition_info compression partition_merge partition_aggregate partition_split tuplesort stats partition_join partition_prune indexing ok 204 + partition_merge 698 ms ok 205 + partition_split 1539 ms ok 206 + partition_join 3261 ms ok 207 + partition_prune 3266 ms ok 208 + reloptions 249 ms ok 209 + hash_part 258 ms ok 210 + indexing 4599 ms ok 211 + partition_aggregate 1331 ms ok 212 + partition_info 335 ms ok 213 + tuplesort 1811 ms ok 214 + explain 180 ms ok 215 + compression 697 ms ok 216 + memoize 179 ms ok 217 + stats 1855 ms ok 218 + predicate 142 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 546 ms ok 220 + event_trigger 786 ms ok 221 - event_trigger_login 38 ms ok 222 - fast_default 385 ms ok 223 - tablespace 1086 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-15 00:08:43.091813000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-15 00:10:17.809442000 +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 +-------+------------+---------------+-------------+---------------------- + 37750 | | 0 | 37750 | pktable_pkey + 37747 | | 0 | 37747 | pktable + 37753 | | 0 | 37753 | fktable + 38273 | | 0 | 38278 | foo + 38282 | | 0 | 38282 | pg_toast_38273_index + 38281 | | 0 | 38281 | pg_toast_38273 + 38556 | | 0 | 38556 | old_oids + 38575 | | 0 | 38575 | pg_toast_38572 + 38576 | | 0 | 38576 | pg_toast_38572_index + 38572 | | 0 | 38572 | recur2 + 38567 | | 0 | 38567 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [00:10:24.900](59.270s) not ok 5 - regression tests pass [00:10:24.901](0.001s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [00:10:24.901](0.000s) # got: '256' # expected: '0' # Checking port 65022 # Found port 65022 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=65022 host=/tmp/RCCq6QbaT4 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [00:10:24.905](0.005s) # 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=65021 host=/tmp/RCCq6QbaT4 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_BZRZ/dump1.sql [00:10:29.474](4.569s) 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/RCCq6QbaT4 -p 65021 -P 65022 --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 [00:10:29.654](0.180s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [00:10:29.654](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/RCCq6QbaT4 -p 65021 -P 65022 --link --check [00:10:30.167](0.513s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [00:10:30.168](0.002s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [00:10:30.171](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 18623 ### 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/RCCq6QbaT4 -p 65021 -P 65022 --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* [00:10:31.954](1.783s) ok 12 - run of pg_upgrade --check for new instance [00:10:31.954](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/RCCq6QbaT4 -p 65021 -P 65022 --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 [00:10:54.965](23.010s) ok 14 - run of pg_upgrade for new instance [00:10:54.965](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 23006 [00:10:55.094](0.129s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=65022 host=/tmp/RCCq6QbaT4 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_BZRZ/dump2.sql [00:10:57.130](2.036s) ok 17 - dump after running pg_upgrade [00:10:57.211](0.081s) ok 18 - old and new dumps match after pg_upgrade [00:10:57.211](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" [00:10:57.317](0.106s) # Looks like you failed 1 test of 18.