[08:34:14.504](0.032s) # testing using transfer mode --link # Checking port 53109 # Found port 53109 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=53109 host=/tmp/csB35BIYXn Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [08:34:14.510](0.006s) # 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 6065 [08:34:16.527](2.018s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [08:34:16.667](0.140s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [08:34:16.799](0.131s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [08:34:16.844](0.045s) ok 4 - created database with ASCII characters from 91 to 127 [08:34:16.846](0.002s) # running regression tests in old instance # using postmaster on /tmp/csB35BIYXn, port 53109 ok 1 - test_setup 321 ms # parallel group (20 tests): varchar char txid name pg_lsn oid text int2 int4 regproc uuid money float4 float8 bit boolean int8 enum rangetypes numeric ok 2 + boolean 367 ms ok 3 + char 132 ms ok 4 + name 171 ms ok 5 + varchar 94 ms ok 6 + text 223 ms ok 7 + int2 232 ms ok 8 + int4 251 ms ok 9 + int8 392 ms ok 10 + oid 184 ms ok 11 + float4 298 ms ok 12 + float8 330 ms ok 13 + bit 354 ms ok 14 + numeric 994 ms ok 15 + txid 145 ms ok 16 + uuid 267 ms ok 17 + enum 402 ms ok 18 + money 279 ms ok 19 + rangetypes 900 ms ok 20 + pg_lsn 174 ms ok 21 + regproc 260 ms # parallel group (20 tests): md5 path lseg circle line time point macaddr timetz macaddr8 numerology inet polygon date box timestamp interval timestamptz strings multirangetypes ok 22 + strings 636 ms ok 23 + md5 75 ms ok 24 + numerology 311 ms ok 25 + point 178 ms ok 26 + lseg 112 ms ok 27 + line 165 ms ok 28 + box 480 ms ok 29 + path 100 ms ok 30 + polygon 354 ms ok 31 + circle 115 ms ok 32 + date 450 ms ok 33 + time 169 ms ok 34 + timetz 205 ms ok 35 + timestamp 534 ms ok 36 + timestamptz 618 ms ok 37 + interval 603 ms ok 38 + inet 343 ms ok 39 + macaddr 205 ms ok 40 + macaddr8 283 ms ok 41 + multirangetypes 764 ms # parallel group (12 tests): comments misc_sanity unicode mvcc type_sanity xid tstypes expressions horology regex geometry opr_sanity ok 42 + geometry 340 ms ok 43 + horology 327 ms ok 44 + tstypes 249 ms ok 45 + regex 339 ms ok 46 + type_sanity 201 ms ok 47 + opr_sanity 455 ms ok 48 + misc_sanity 34 ms ok 49 + comments 28 ms ok 50 + expressions 268 ms ok 51 + unicode 71 ms ok 52 + xid 216 ms ok 53 + mvcc 81 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 440 ms ok 55 + copyselect 141 ms ok 56 + copydml 134 ms ok 57 + insert 1312 ms ok 58 + insert_conflict 922 ms # parallel group (7 tests): create_function_c create_schema create_operator create_type create_misc create_procedure create_table ok 59 + create_function_c 21 ms ok 60 + create_misc 157 ms ok 61 + create_operator 110 ms ok 62 + create_procedure 161 ms ok 63 + create_table 1585 ms ok 64 + create_type 131 ms ok 65 + create_schema 101 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2023 ms ok 67 + create_index_spgist 926 ms ok 68 + create_view 1185 ms ok 69 + index_including 552 ms ok 70 + index_including_gist 478 ms # parallel group (16 tests): select create_cast hash_func errors create_aggregate roleattributes drop_if_exists typed_table infinite_recurse create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 215 ms ok 72 + create_function_sql 531 ms ok 73 + create_cast 167 ms ok 74 + constraints 1479 ms ok 75 + triggers 5139 ms ok 76 + select 154 ms ok 77 + inherit 4033 ms ok 78 + typed_table 332 ms ok 79 + vacuum 988 ms ok 80 + drop_if_exists 302 ms ok 81 + updatable_views 3354 ms ok 82 + roleattributes 272 ms ok 83 + create_am 454 ms ok 84 + hash_func 183 ms ok 85 + errors 191 ms ok 86 + infinite_recurse 419 ms ok 87 - sanity_check 223 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit random namespace case select_distinct select_into prepared_xacts union portals transactions subselect arrays hash_index update aggregates btree_index join ok 88 + select_into 395 ms ok 89 + select_distinct 391 ms ok 90 + select_distinct_on 100 ms ok 91 + select_implicit 219 ms ok 92 + select_having 185 ms ok 93 + subselect 928 ms ok 94 + union 786 ms ok 95 + case 331 ms ok 96 + join 2392 ms ok 97 + aggregates 1802 ms ok 98 + transactions 880 ms ok 99 + random 271 ms ok 100 + portals 825 ms ok 101 + arrays 1074 ms ok 102 + btree_index 2132 ms ok 103 + hash_index 1086 ms ok 104 + update 1370 ms ok 105 + delete 108 ms ok 106 + namespace 324 ms ok 107 + prepared_xacts 434 ms # parallel group (20 tests): drop_operator init_privs security_label password tablesample lock object_address collate groupingsets replica_identity spgist gin gist brin matview identity generated join_hash rowsecurity privileges ok 108 + brin 1501 ms ok 109 + gin 1482 ms ok 110 + gist 1486 ms ok 111 + spgist 1273 ms ok 112 + privileges 4407 ms ok 113 + init_privs 135 ms ok 114 + security_label 333 ms ok 115 + collate 1180 ms ok 116 + matview 1735 ms ok 117 + lock 842 ms ok 118 + replica_identity 1218 ms ok 119 + rowsecurity 4174 ms ok 120 + object_address 1093 ms ok 121 + tablesample 483 ms ok 122 + groupingsets 1187 ms ok 123 + drop_operator 96 ms ok 124 + password 456 ms ok 125 + identity 2058 ms ok 126 + generated 3530 ms ok 127 + join_hash 3960 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 195 ms ok 129 + brin_multi 1071 ms # parallel group (18 tests): async dbsize sysviews collate.utf8 tidscan tidrangescan tid tsrf alter_operator misc_functions misc create_role incremental_sort alter_generic merge collate.icu.utf8 create_table_like without_overlaps ok 130 + create_table_like 1314 ms ok 131 + alter_generic 721 ms ok 132 + alter_operator 330 ms ok 133 + misc 413 ms ok 134 + async 101 ms ok 135 + dbsize 141 ms ok 136 + merge 1193 ms ok 137 + misc_functions 355 ms ok 138 + sysviews 157 ms ok 139 + tsrf 298 ms ok 140 + tid 236 ms ok 141 + tidscan 204 ms ok 142 + tidrangescan 236 ms ok 143 + collate.utf8 175 ms ok 144 + collate.icu.utf8 1280 ms ok 145 + incremental_sort 501 ms ok 146 + create_role 425 ms ok 147 + without_overlaps 1567 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 psql_crosstab amutils rules psql stats_ext ok 148 + rules 1267 ms ok 149 + psql 1434 ms ok 150 + psql_crosstab 74 ms ok 151 + amutils 101 ms ok 152 + stats_ext 3135 ms ok 153 + collate.linux.utf8 14 ms ok 154 + collate.windows.win1252 21 ms ok 155 - select_parallel 1786 ms ok 156 - write_parallel 152 ms ok 157 - vacuum_parallel 130 ms # parallel group (2 tests): subscription publication ok 158 + publication 1873 ms ok 159 + subscription 481 ms # parallel group (17 tests): advisory_lock combocid xmlmap portals_p2 functional_deps select_views tsdicts dependency bitmapops equivclass indirect_toast guc window tsearch cluster foreign_data foreign_key ok 160 + select_views 531 ms ok 161 + portals_p2 278 ms ok 162 + foreign_key 6284 ms ok 163 + cluster 1140 ms ok 164 + dependency 546 ms ok 165 + guc 613 ms ok 166 + bitmapops 557 ms ok 167 + combocid 257 ms ok 168 + tsearch 1071 ms ok 169 + tsdicts 531 ms ok 170 + foreign_data 3189 ms ok 171 + window 1033 ms ok 172 + xmlmap 263 ms ok 173 + functional_deps 348 ms ok 174 + advisory_lock 144 ms ok 175 + indirect_toast 612 ms ok 176 + equivclass 565 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable sqljson_queryfuncs sqljson jsonpath json jsonb_jsonpath jsonb ok 177 + json 733 ms ok 178 + jsonb 974 ms ok 179 + json_encoding 171 ms ok 180 + jsonpath 567 ms ok 181 + jsonpath_encoding 140 ms ok 182 + jsonb_jsonpath 880 ms ok 183 + sqljson 513 ms ok 184 + sqljson_queryfuncs 501 ms ok 185 + sqljson_jsontable 272 ms # parallel group (18 tests): prepare conversion returning limit plancache rowtypes temp with truncate copy2 sequence largeobject polymorphism xml rangefuncs domain plpgsql alter_table ok 186 + plancache 661 ms ok 187 + limit 490 ms ok 188 + plpgsql 3342 ms ok 189 + copy2 1130 ms ok 190 + temp 998 ms ok 191 + domain 1544 ms ok 192 + rangefuncs 1439 ms ok 193 + prepare 237 ms ok 194 + conversion 409 ms ok 195 + truncate 1113 ms not ok 196 + alter_table 8519 ms ok 197 + sequence 1155 ms ok 198 + polymorphism 1350 ms ok 199 + rowtypes 992 ms ok 200 + returning 449 ms ok 201 + largeobject 1310 ms ok 202 + with 1090 ms ok 203 + xml 1423 ms # parallel group (15 tests): predicate hash_part reloptions memoize partition_info explain compression partition_aggregate partition_merge tuplesort stats partition_split partition_join partition_prune indexing ok 204 + partition_merge 1501 ms ok 205 + partition_split 2998 ms ok 206 + partition_join 5176 ms ok 207 + partition_prune 5593 ms ok 208 + reloptions 308 ms ok 209 + hash_part 185 ms ok 210 + indexing 5817 ms ok 211 + partition_aggregate 1485 ms ok 212 + partition_info 454 ms ok 213 + tuplesort 2005 ms ok 214 + explain 595 ms ok 215 + compression 813 ms ok 216 + memoize 445 ms ok 217 + stats 2198 ms ok 218 + predicate 62 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 369 ms ok 220 + event_trigger 453 ms ok 221 - event_trigger_login 62 ms ok 222 - fast_default 621 ms ok 223 - tablespace 1991 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-08 08:33:34.085320000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-08 08:35:02.911900000 +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 +-------+------------+---------------+-------------+---------------------- + 37737 | | 0 | 37737 | pktable_pkey + 37734 | | 0 | 37734 | pktable + 37739 | | 0 | 37739 | fktable + 38259 | | 0 | 38264 | foo + 38268 | | 0 | 38268 | pg_toast_38259_index + 38267 | | 0 | 38267 | pg_toast_38259 + 38560 | | 0 | 38560 | old_oids + 38577 | | 0 | 38577 | pg_toast_38574 + 38578 | | 0 | 38578 | pg_toast_38574_index + 38574 | | 0 | 38574 | recur2 + 38569 | | 0 | 38569 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [08:35:11.995](55.149s) not ok 5 - regression tests pass [08:35:11.995](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [08:35:11.995](0.000s) # got: '256' # expected: '0' # Checking port 53110 # Found port 53110 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=53110 host=/tmp/csB35BIYXn Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [08:35:11.998](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=53109 host=/tmp/csB35BIYXn dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_o99e/dump1.sql [08:35:16.210](4.212s) 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/csB35BIYXn -p 53109 -P 53110 --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 [08:35:16.365](0.155s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [08:35:16.366](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/csB35BIYXn -p 53109 -P 53110 --link --check [08:35:17.045](0.679s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [08:35:17.046](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [08:35:17.048](0.001s) 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 18174 ### 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/csB35BIYXn -p 53109 -P 53110 --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* [08:35:18.880](1.832s) ok 12 - run of pg_upgrade --check for new instance [08:35:18.880](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/csB35BIYXn -p 53109 -P 53110 --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 [08:35:39.096](20.216s) ok 14 - run of pg_upgrade for new instance [08:35:39.096](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 21862 [08:35:39.221](0.125s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=53110 host=/tmp/csB35BIYXn dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_o99e/dump2.sql [08:35:41.403](2.182s) ok 17 - dump after running pg_upgrade [08:35:41.486](0.083s) ok 18 - old and new dumps match after pg_upgrade [08:35:41.486](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" [08:35:41.596](0.110s) # Looks like you failed 1 test of 18.