[07:08:57.937](0.014s) # testing using transfer mode --link # Checking port 61839 # Found port 61839 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=61839 host=/tmp/2wT2LFidYQ Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [07:08:57.998](0.061s) # 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 6078 [07:09:00.193](2.195s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [07:09:00.360](0.167s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [07:09:00.525](0.165s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [07:09:00.604](0.079s) ok 4 - created database with ASCII characters from 91 to 127 [07:09:00.606](0.002s) # running regression tests in old instance # using postmaster on /tmp/2wT2LFidYQ, port 61839 ok 1 - test_setup 362 ms # parallel group (20 tests): varchar char oid pg_lsn name txid uuid int2 text int4 boolean regproc money float4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 317 ms ok 3 + char 144 ms ok 4 + name 193 ms ok 5 + varchar 94 ms ok 6 + text 257 ms ok 7 + int2 250 ms ok 8 + int4 292 ms ok 9 + int8 376 ms ok 10 + oid 151 ms ok 11 + float4 352 ms ok 12 + float8 414 ms ok 13 + bit 414 ms ok 14 + numeric 1060 ms ok 15 + txid 203 ms ok 16 + uuid 231 ms ok 17 + enum 420 ms ok 18 + money 338 ms ok 19 + rangetypes 876 ms ok 20 + pg_lsn 158 ms ok 21 + regproc 321 ms # parallel group (20 tests): lseg md5 circle path time macaddr point line timetz macaddr8 numerology inet polygon date box timestamp interval strings timestamptz multirangetypes ok 22 + strings 670 ms ok 23 + md5 74 ms ok 24 + numerology 241 ms ok 25 + point 127 ms ok 26 + lseg 69 ms ok 27 + line 139 ms ok 28 + box 451 ms ok 29 + path 111 ms ok 30 + polygon 317 ms ok 31 + circle 86 ms ok 32 + date 344 ms ok 33 + time 122 ms ok 34 + timetz 154 ms ok 35 + timestamp 587 ms ok 36 + timestamptz 680 ms ok 37 + interval 591 ms ok 38 + inet 288 ms ok 39 + macaddr 125 ms ok 40 + macaddr8 209 ms ok 41 + multirangetypes 846 ms # parallel group (12 tests): unicode misc_sanity comments mvcc expressions xid type_sanity tstypes geometry horology regex opr_sanity ok 42 + geometry 358 ms ok 43 + horology 387 ms ok 44 + tstypes 297 ms ok 45 + regex 392 ms ok 46 + type_sanity 217 ms ok 47 + opr_sanity 541 ms ok 48 + misc_sanity 39 ms ok 49 + comments 46 ms ok 50 + expressions 204 ms ok 51 + unicode 34 ms ok 52 + xid 206 ms ok 53 + mvcc 104 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 314 ms ok 55 + copyselect 140 ms ok 56 + copydml 182 ms ok 57 + insert 1082 ms ok 58 + insert_conflict 705 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 25 ms ok 60 + create_misc 177 ms ok 61 + create_operator 86 ms ok 62 + create_procedure 176 ms ok 63 + create_table 1684 ms ok 64 + create_type 158 ms ok 65 + create_schema 96 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1823 ms ok 67 + create_index_spgist 909 ms ok 68 + create_view 1166 ms ok 69 + index_including 679 ms ok 70 + index_including_gist 636 ms # parallel group (16 tests): create_cast hash_func errors roleattributes typed_table create_aggregate select infinite_recurse drop_if_exists create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 466 ms ok 72 + create_function_sql 582 ms ok 73 + create_cast 98 ms ok 74 + constraints 1362 ms ok 75 + triggers 4270 ms ok 76 + select 508 ms ok 77 + inherit 3813 ms ok 78 + typed_table 381 ms ok 79 + vacuum 931 ms ok 80 + drop_if_exists 572 ms ok 81 + updatable_views 2711 ms ok 82 + roleattributes 363 ms ok 83 + create_am 624 ms ok 84 + hash_func 128 ms ok 85 + errors 254 ms ok 86 + infinite_recurse 535 ms ok 87 - sanity_check 268 ms # parallel group (20 tests): delete select_distinct_on select_having namespace random case select_implicit prepared_xacts select_distinct select_into union hash_index subselect transactions portals arrays update aggregates btree_index join ok 88 + select_into 878 ms ok 89 + select_distinct 827 ms ok 90 + select_distinct_on 276 ms ok 91 + select_implicit 778 ms ok 92 + select_having 406 ms ok 93 + subselect 1965 ms ok 94 + union 1639 ms ok 95 + case 769 ms ok 96 + join 3446 ms ok 97 + aggregates 2996 ms ok 98 + transactions 1995 ms ok 99 + random 641 ms ok 100 + portals 2042 ms ok 101 + arrays 2126 ms ok 102 + btree_index 3246 ms ok 103 + hash_index 1943 ms ok 104 + update 2349 ms ok 105 + delete 261 ms ok 106 + namespace 622 ms ok 107 + prepared_xacts 805 ms # parallel group (20 tests): init_privs drop_operator password security_label tablesample object_address lock groupingsets spgist collate gin replica_identity gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 4041 ms ok 109 + gin 1519 ms ok 110 + gist 1579 ms ok 111 + spgist 1365 ms ok 112 + privileges 4484 ms ok 113 + init_privs 81 ms ok 114 + security_label 422 ms ok 115 + collate 1465 ms ok 116 + matview 1906 ms ok 117 + lock 964 ms ok 118 + replica_identity 1523 ms ok 119 + rowsecurity 4155 ms ok 120 + object_address 864 ms ok 121 + tablesample 504 ms ok 122 + groupingsets 1119 ms ok 123 + drop_operator 139 ms ok 124 + password 334 ms ok 125 + identity 2207 ms ok 126 + generated 2668 ms ok 127 + join_hash 4119 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 171 ms ok 129 + brin_multi 1154 ms # parallel group (18 tests): async dbsize sysviews collate.utf8 tidscan tid tidrangescan tsrf alter_operator misc misc_functions create_role incremental_sort alter_generic create_table_like merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 1181 ms ok 131 + alter_generic 911 ms ok 132 + alter_operator 390 ms ok 133 + misc 451 ms ok 134 + async 65 ms ok 135 + dbsize 154 ms ok 136 + merge 1242 ms ok 137 + misc_functions 479 ms ok 138 + sysviews 162 ms ok 139 + tsrf 373 ms ok 140 + tid 298 ms ok 141 + tidscan 262 ms ok 142 + tidrangescan 306 ms ok 143 + collate.utf8 213 ms ok 144 + collate.icu.utf8 1294 ms ok 145 + incremental_sort 544 ms ok 146 + create_role 536 ms ok 147 + without_overlaps 1568 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1335 ms ok 149 + psql 1339 ms ok 150 + psql_crosstab 143 ms ok 151 + amutils 119 ms ok 152 + stats_ext 2461 ms ok 153 + collate.linux.utf8 25 ms ok 154 + collate.windows.win1252 43 ms ok 155 - select_parallel 1520 ms ok 156 - write_parallel 123 ms ok 157 - vacuum_parallel 117 ms # parallel group (2 tests): subscription publication ok 158 + publication 3090 ms ok 159 + subscription 222 ms # parallel group (17 tests): advisory_lock portals_p2 combocid xmlmap tsdicts functional_deps dependency select_views guc equivclass bitmapops indirect_toast window tsearch cluster foreign_data foreign_key ok 160 + select_views 447 ms ok 161 + portals_p2 165 ms ok 162 + foreign_key 6214 ms ok 163 + cluster 1315 ms ok 164 + dependency 429 ms ok 165 + guc 490 ms ok 166 + bitmapops 534 ms ok 167 + combocid 180 ms ok 168 + tsearch 921 ms ok 169 + tsdicts 363 ms ok 170 + foreign_data 3068 ms ok 171 + window 763 ms ok 172 + xmlmap 183 ms ok 173 + functional_deps 385 ms ok 174 + advisory_lock 133 ms ok 175 + indirect_toast 538 ms ok 176 + equivclass 518 ms # parallel group (8 tests): jsonpath_encoding json_encoding sqljson jsonpath sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 807 ms ok 178 + jsonb 1311 ms ok 179 + json_encoding 137 ms ok 180 + jsonpath 409 ms ok 181 + jsonpath_encoding 107 ms ok 182 + jsonb_jsonpath 955 ms ok 183 + sqljson 405 ms ok 184 + sqljson_queryfuncs 671 ms # parallel group (18 tests): prepare returning conversion limit plancache temp rowtypes sequence with largeobject rangefuncs polymorphism xml copy2 truncate domain plpgsql alter_table ok 185 + plancache 681 ms ok 186 + limit 430 ms ok 187 + plpgsql 3656 ms ok 188 + copy2 1342 ms ok 189 + temp 745 ms ok 190 + domain 1736 ms ok 191 + rangefuncs 1300 ms ok 192 + prepare 199 ms ok 193 + conversion 381 ms ok 194 + truncate 1381 ms not ok 195 + alter_table 8602 ms ok 196 + sequence 1085 ms ok 197 + polymorphism 1308 ms ok 198 + rowtypes 1009 ms ok 199 + returning 357 ms ok 200 + largeobject 1278 ms ok 201 + with 1159 ms ok 202 + xml 1314 ms # parallel group (13 tests): predicate hash_part memoize reloptions explain partition_info compression partition_aggregate tuplesort stats partition_join partition_prune indexing ok 203 + partition_join 4153 ms ok 204 + partition_prune 5286 ms ok 205 + reloptions 460 ms ok 206 + hash_part 267 ms ok 207 + indexing 6436 ms ok 208 + partition_aggregate 1491 ms ok 209 + partition_info 482 ms ok 210 + tuplesort 1717 ms ok 211 + explain 467 ms ok 212 + compression 1084 ms ok 213 + memoize 433 ms ok 214 + stats 1827 ms ok 215 + predicate 101 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 376 ms ok 217 + event_trigger 464 ms ok 218 - event_trigger_login 39 ms ok 219 - fast_default 392 ms ok 220 - tablespace 2023 ms 1..220 # 1 of 220 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-03-29 07:08:18.043762000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-03-29 07:09:47.442865000 +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 +-------+------------+---------------+-------------+---------------------- + 37624 | | 0 | 37624 | pktable + 37629 | | 0 | 37629 | fktable + 37627 | | 0 | 37627 | pktable_pkey + 38186 | | 0 | 38191 | foo + 38195 | | 0 | 38195 | pg_toast_38186_index + 38194 | | 0 | 38194 | pg_toast_38186 + 38424 | | 0 | 38424 | old_oids + 38473 | | 0 | 38473 | pg_toast_38466 + 38475 | | 0 | 38475 | pg_toast_38466_index + 38466 | | 0 | 38466 | recur2 + 38460 | | 0 | 38460 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [07:09:57.006](56.401s) not ok 5 - regression tests pass [07:09:57.007](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [07:09:57.007](0.000s) # got: '256' # expected: '0' # Checking port 61840 # Found port 61840 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=61840 host=/tmp/2wT2LFidYQ Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [07:09:57.009](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=61839 host=/tmp/2wT2LFidYQ dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_fd7o/dump1.sql [07:10:02.142](5.133s) 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/2wT2LFidYQ -p 61839 -P 61840 --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 [07:10:02.315](0.173s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [07:10:02.315](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/2wT2LFidYQ -p 61839 -P 61840 --link --check [07:10:02.943](0.628s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [07:10:02.943](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [07:10:02.943](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 18331 ### 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/2wT2LFidYQ -p 61839 -P 61840 --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* [07:10:05.006](2.063s) ok 12 - run of pg_upgrade --check for new instance [07:10:05.009](0.003s) 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/2wT2LFidYQ -p 61839 -P 61840 --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 [07:10:23.552](18.543s) ok 14 - run of pg_upgrade for new instance [07:10:23.552](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 21703 [07:10:23.678](0.126s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=61840 host=/tmp/2wT2LFidYQ dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_fd7o/dump2.sql [07:10:25.864](2.186s) ok 17 - dump after running pg_upgrade [07:10:25.948](0.084s) ok 18 - old and new dumps match after pg_upgrade [07:10:25.949](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" [07:10:26.070](0.122s) # Looks like you failed 1 test of 18.