[16:06:27.116](0.030s) # testing using transfer mode --link # Checking port 60267 # Found port 60267 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=60267 host=/tmp/B08ezpiUwy Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [16:06:27.132](0.016s) # 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 6101 [16:06:29.214](2.082s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [16:06:29.291](0.077s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [16:06:29.389](0.098s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [16:06:29.453](0.063s) ok 4 - created database with ASCII characters from 91 to 127 [16:06:29.455](0.003s) # running regression tests in old instance # using postmaster on /tmp/B08ezpiUwy, port 60267 ok 1 - test_setup 572 ms # parallel group (20 tests): varchar char pg_lsn oid uuid txid name text int2 int4 money regproc boolean float4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 312 ms ok 3 + char 148 ms ok 4 + name 225 ms ok 5 + varchar 147 ms ok 6 + text 243 ms ok 7 + int2 244 ms ok 8 + int4 247 ms ok 9 + int8 377 ms ok 10 + oid 186 ms ok 11 + float4 321 ms ok 12 + float8 425 ms ok 13 + bit 419 ms ok 14 + numeric 1046 ms ok 15 + txid 204 ms ok 16 + uuid 200 ms ok 17 + enum 517 ms ok 18 + money 286 ms ok 19 + rangetypes 888 ms ok 20 + pg_lsn 184 ms ok 21 + regproc 308 ms # parallel group (20 tests): md5 path lseg circle line time macaddr point timetz macaddr8 inet polygon numerology date box timestamp interval timestamptz strings multirangetypes ok 22 + strings 782 ms ok 23 + md5 75 ms ok 24 + numerology 363 ms ok 25 + point 193 ms ok 26 + lseg 89 ms ok 27 + line 123 ms ok 28 + box 500 ms ok 29 + path 81 ms ok 30 + polygon 356 ms ok 31 + circle 106 ms ok 32 + date 378 ms ok 33 + time 124 ms ok 34 + timetz 204 ms ok 35 + timestamp 635 ms ok 36 + timestamptz 776 ms ok 37 + interval 656 ms ok 38 + inet 350 ms ok 39 + macaddr 145 ms ok 40 + macaddr8 267 ms ok 41 + multirangetypes 940 ms # parallel group (12 tests): comments misc_sanity unicode mvcc expressions xid tstypes geometry type_sanity regex opr_sanity horology ok 42 + geometry 342 ms ok 43 + horology 491 ms ok 44 + tstypes 320 ms ok 45 + regex 364 ms ok 46 + type_sanity 359 ms ok 47 + opr_sanity 455 ms ok 48 + misc_sanity 53 ms ok 49 + comments 51 ms ok 50 + expressions 195 ms ok 51 + unicode 58 ms ok 52 + xid 197 ms ok 53 + mvcc 101 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 323 ms ok 55 + copyselect 82 ms ok 56 + copydml 91 ms ok 57 + insert 1089 ms ok 58 + insert_conflict 568 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_procedure create_misc create_table ok 59 + create_function_c 21 ms ok 60 + create_misc 193 ms ok 61 + create_operator 96 ms ok 62 + create_procedure 133 ms ok 63 + create_table 1150 ms ok 64 + create_type 120 ms ok 65 + create_schema 109 ms # parallel group (5 tests): index_including index_including_gist create_index_spgist create_view create_index ok 66 + create_index 2576 ms ok 67 + create_index_spgist 1268 ms ok 68 + create_view 1409 ms ok 69 + index_including 608 ms ok 70 + index_including_gist 654 ms # parallel group (16 tests): create_cast hash_func errors roleattributes create_aggregate select typed_table infinite_recurse drop_if_exists create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 222 ms ok 72 + create_function_sql 598 ms ok 73 + create_cast 133 ms ok 74 + constraints 1567 ms ok 75 + triggers 5643 ms ok 76 + select 295 ms ok 77 + inherit 4187 ms ok 78 + typed_table 357 ms ok 79 + vacuum 1169 ms ok 80 + drop_if_exists 423 ms ok 81 + updatable_views 3397 ms ok 82 + roleattributes 216 ms ok 83 + create_am 524 ms ok 84 + hash_func 157 ms ok 85 + errors 185 ms ok 86 + infinite_recurse 378 ms ok 87 - sanity_check 132 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit namespace random case prepared_xacts select_distinct select_into union subselect portals transactions hash_index arrays update aggregates join btree_index ok 88 + select_into 516 ms ok 89 + select_distinct 491 ms ok 90 + select_distinct_on 98 ms ok 91 + select_implicit 265 ms ok 92 + select_having 209 ms ok 93 + subselect 1020 ms ok 94 + union 748 ms ok 95 + case 450 ms ok 96 + join 2231 ms ok 97 + aggregates 2199 ms ok 98 + transactions 1060 ms ok 99 + random 408 ms ok 100 + portals 1034 ms ok 101 + arrays 1236 ms ok 102 + btree_index 2327 ms ok 103 + hash_index 1069 ms ok 104 + update 1565 ms ok 105 + delete 116 ms ok 106 + namespace 403 ms ok 107 + prepared_xacts 477 ms # parallel group (20 tests): init_privs tablesample security_label drop_operator password lock object_address replica_identity collate spgist groupingsets gist gin matview identity generated brin join_hash privileges rowsecurity ok 108 + brin 3952 ms ok 109 + gin 1445 ms ok 110 + gist 1391 ms ok 111 + spgist 1243 ms ok 112 + privileges 4352 ms ok 113 + init_privs 53 ms ok 114 + security_label 474 ms ok 115 + collate 1201 ms ok 116 + matview 2071 ms ok 117 + lock 931 ms ok 118 + replica_identity 1163 ms ok 119 + rowsecurity 4647 ms ok 120 + object_address 1139 ms ok 121 + tablesample 362 ms ok 122 + groupingsets 1318 ms ok 123 + drop_operator 478 ms ok 124 + password 729 ms ok 125 + identity 2163 ms ok 126 + generated 3663 ms ok 127 + join_hash 4002 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 154 ms ok 129 + brin_multi 878 ms # parallel group (18 tests): async collate.utf8 dbsize tidscan sysviews tidrangescan tid tsrf alter_operator misc misc_functions create_role incremental_sort alter_generic create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 1129 ms ok 131 + alter_generic 646 ms ok 132 + alter_operator 284 ms ok 133 + misc 378 ms ok 134 + async 62 ms ok 135 + dbsize 151 ms ok 136 + merge 1265 ms ok 137 + misc_functions 386 ms ok 138 + sysviews 177 ms ok 139 + tsrf 273 ms ok 140 + tid 263 ms ok 141 + tidscan 159 ms ok 142 + tidrangescan 178 ms ok 143 + collate.utf8 149 ms ok 144 + collate.icu.utf8 1259 ms ok 145 + incremental_sort 442 ms ok 146 + create_role 421 ms ok 147 + without_overlaps 1640 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1878 ms ok 149 + psql 1739 ms ok 150 + psql_crosstab 88 ms ok 151 + amutils 56 ms ok 152 + stats_ext 3421 ms ok 153 + collate.linux.utf8 25 ms ok 154 + collate.windows.win1252 27 ms ok 155 - select_parallel 1620 ms ok 156 - write_parallel 209 ms ok 157 - vacuum_parallel 229 ms # parallel group (2 tests): subscription publication ok 158 + publication 1559 ms ok 159 + subscription 474 ms # parallel group (17 tests): advisory_lock portals_p2 combocid xmlmap functional_deps select_views equivclass dependency indirect_toast bitmapops tsdicts guc tsearch window cluster foreign_data foreign_key ok 160 + select_views 374 ms ok 161 + portals_p2 264 ms ok 162 + foreign_key 6467 ms ok 163 + cluster 1089 ms ok 164 + dependency 506 ms ok 165 + guc 629 ms ok 166 + bitmapops 554 ms ok 167 + combocid 265 ms ok 168 + tsearch 878 ms ok 169 + tsdicts 575 ms ok 170 + foreign_data 2822 ms ok 171 + window 902 ms ok 172 + xmlmap 282 ms ok 173 + functional_deps 309 ms ok 174 + advisory_lock 194 ms ok 175 + indirect_toast 512 ms ok 176 + equivclass 463 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 959 ms ok 178 + jsonb 1317 ms ok 179 + json_encoding 453 ms ok 180 + jsonpath 609 ms ok 181 + jsonpath_encoding 183 ms ok 182 + jsonb_jsonpath 1126 ms ok 183 + sqljson 724 ms ok 184 + sqljson_queryfuncs 825 ms ok 185 + sqljson_jsontable 548 ms # parallel group (18 tests): prepare conversion returning limit plancache temp rowtypes sequence truncate copy2 with largeobject xml rangefuncs polymorphism domain plpgsql alter_table ok 186 + plancache 553 ms ok 187 + limit 513 ms ok 188 + plpgsql 3445 ms ok 189 + copy2 1222 ms ok 190 + temp 684 ms ok 191 + domain 1732 ms ok 192 + rangefuncs 1575 ms ok 193 + prepare 169 ms ok 194 + conversion 311 ms ok 195 + truncate 1209 ms not ok 196 + alter_table 11703 ms ok 197 + sequence 1082 ms ok 198 + polymorphism 1575 ms ok 199 + rowtypes 1059 ms ok 200 + returning 382 ms ok 201 + largeobject 1279 ms ok 202 + with 1239 ms ok 203 + xml 1521 ms # parallel group (15 tests): hash_part predicate explain partition_info memoize reloptions compression partition_merge partition_aggregate stats partition_split tuplesort partition_join partition_prune indexing ok 204 + partition_merge 855 ms ok 205 + partition_split 1676 ms ok 206 + partition_join 3146 ms ok 207 + partition_prune 3403 ms ok 208 + reloptions 371 ms ok 209 + hash_part 164 ms ok 210 + indexing 3753 ms ok 211 + partition_aggregate 1566 ms ok 212 + partition_info 299 ms ok 213 + tuplesort 1920 ms ok 214 + explain 298 ms ok 215 + compression 647 ms ok 216 + memoize 369 ms ok 217 + stats 1661 ms ok 218 + predicate 162 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 466 ms ok 220 + event_trigger 550 ms ok 221 - event_trigger_login 34 ms ok 222 - fast_default 403 ms ok 223 - tablespace 1777 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-11 16:05:46.164026000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-11 16:07:20.009887000 +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 +-------+------------+---------------+-------------+---------------------- + 37723 | | 0 | 37723 | pktable_pkey + 37720 | | 0 | 37720 | pktable + 37735 | | 0 | 37735 | fktable + 38281 | | 0 | 38289 | foo + 38293 | | 0 | 38293 | pg_toast_38281_index + 38292 | | 0 | 38292 | pg_toast_38281 + 38567 | | 0 | 38567 | old_oids + 38584 | | 0 | 38584 | pg_toast_38581 + 38585 | | 0 | 38585 | pg_toast_38581_index + 38581 | | 0 | 38581 | recur2 + 38576 | | 0 | 38576 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [16:07:26.730](57.275s) not ok 5 - regression tests pass [16:07:26.730](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [16:07:26.731](0.000s) # got: '256' # expected: '0' # Checking port 60268 # Found port 60268 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=60268 host=/tmp/B08ezpiUwy Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [16:07:26.734](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=60267 host=/tmp/B08ezpiUwy dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_QC7U/dump1.sql [16:07:31.589](4.856s) 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/B08ezpiUwy -p 60267 -P 60268 --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 [16:07:31.751](0.162s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [16:07:31.751](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/B08ezpiUwy -p 60267 -P 60268 --link --check [16:07:32.519](0.767s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [16:07:32.519](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [16:07:32.519](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 18275 ### 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/B08ezpiUwy -p 60267 -P 60268 --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* [16:07:34.151](1.632s) ok 12 - run of pg_upgrade --check for new instance [16:07:34.159](0.008s) 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/B08ezpiUwy -p 60267 -P 60268 --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 [16:07:55.162](21.002s) ok 14 - run of pg_upgrade for new instance [16:07:55.162](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 21957 [16:07:55.285](0.123s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=60268 host=/tmp/B08ezpiUwy dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_QC7U/dump2.sql [16:07:57.727](2.442s) ok 17 - dump after running pg_upgrade [16:07:57.806](0.079s) ok 18 - old and new dumps match after pg_upgrade [16:07:57.806](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" [16:07:57.912](0.106s) # Looks like you failed 1 test of 18.