[08:29:23.540](0.013s) # testing using transfer mode --copy # Checking port 51993 # Found port 51993 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=51993 host=/tmp/0tOIvQXIej Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [08:29:23.559](0.019s) # 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: C.UTF-8 LC_NUMERIC: C.UTF-8 LC_TIME: C.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 ... Etc/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 26649 [08:29:25.480](1.921s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [08:29:25.645](0.165s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [08:29:25.808](0.163s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [08:29:25.892](0.084s) ok 4 - created database with ASCII characters from 91 to 127 [08:29:25.893](0.001s) # running regression tests in old instance # using postmaster on /tmp/0tOIvQXIej, port 51993 ok 1 - test_setup 604 ms # parallel group (20 tests): oid char int4 int2 varchar pg_lsn regproc text txid name float4 uuid money int8 float8 enum bit boolean rangetypes numeric ok 2 + boolean 352 ms ok 3 + char 98 ms ok 4 + name 154 ms ok 5 + varchar 128 ms ok 6 + text 146 ms ok 7 + int2 127 ms ok 8 + int4 122 ms ok 9 + int8 189 ms ok 10 + oid 94 ms ok 11 + float4 161 ms ok 12 + float8 211 ms ok 13 + bit 342 ms ok 14 + numeric 1080 ms ok 15 + txid 145 ms ok 16 + uuid 166 ms ok 17 + enum 222 ms ok 18 + money 176 ms ok 19 + rangetypes 1016 ms ok 20 + pg_lsn 130 ms ok 21 + regproc 134 ms # parallel group (20 tests): lseg md5 line timetz path numerology circle time macaddr8 macaddr date inet point strings interval timestamp timestamptz polygon multirangetypes box ok 22 + strings 403 ms ok 23 + md5 71 ms ok 24 + numerology 147 ms ok 25 + point 305 ms ok 26 + lseg 60 ms ok 27 + line 81 ms ok 28 + box 995 ms ok 29 + path 131 ms ok 30 + polygon 861 ms ok 31 + circle 149 ms ok 32 + date 214 ms ok 33 + time 151 ms ok 34 + timetz 88 ms ok 35 + timestamp 537 ms ok 36 + timestamptz 585 ms ok 37 + interval 418 ms ok 38 + inet 244 ms ok 39 + macaddr 160 ms ok 40 + macaddr8 152 ms ok 41 + multirangetypes 962 ms # parallel group (12 tests): unicode misc_sanity comments expressions xid tstypes mvcc type_sanity geometry horology regex opr_sanity ok 42 + geometry 446 ms ok 43 + horology 686 ms ok 44 + tstypes 191 ms ok 45 + regex 817 ms ok 46 + type_sanity 395 ms ok 47 + opr_sanity 1042 ms ok 48 + misc_sanity 64 ms ok 49 + comments 65 ms ok 50 + expressions 110 ms ok 51 + unicode 25 ms ok 52 + xid 160 ms ok 53 + mvcc 193 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 222 ms ok 55 + copyselect 63 ms ok 56 + copydml 61 ms ok 57 + insert 601 ms ok 58 + insert_conflict 299 ms # parallel group (7 tests): create_function_c create_operator create_misc create_schema create_type create_procedure create_table ok 59 + create_function_c 39 ms ok 60 + create_misc 107 ms ok 61 + create_operator 77 ms ok 62 + create_procedure 164 ms ok 63 + create_table 1274 ms ok 64 + create_type 121 ms ok 65 + create_schema 121 ms # parallel group (5 tests): index_including index_including_gist create_view create_index_spgist create_index ok 66 + create_index 1705 ms ok 67 + create_index_spgist 1460 ms ok 68 + create_view 814 ms ok 69 + index_including 375 ms ok 70 + index_including_gist 620 ms # parallel group (16 tests): errors create_cast roleattributes create_aggregate hash_func drop_if_exists typed_table create_am create_function_sql select infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 136 ms ok 72 + create_function_sql 330 ms ok 73 + create_cast 85 ms ok 74 + constraints 1214 ms ok 75 + triggers 3636 ms ok 76 + select 366 ms ok 77 + inherit 2893 ms ok 78 + typed_table 210 ms ok 79 + vacuum 792 ms ok 80 + drop_if_exists 169 ms ok 81 + updatable_views 2301 ms ok 82 + roleattributes 93 ms ok 83 + create_am 300 ms ok 84 + hash_func 147 ms ok 85 + errors 73 ms ok 86 + infinite_recurse 664 ms ok 87 - sanity_check 93 ms # parallel group (20 tests): select_distinct_on select_having delete random case select_implicit select_into namespace prepared_xacts transactions portals arrays union select_distinct subselect hash_index update aggregates join btree_index ok 88 + select_into 212 ms ok 89 + select_distinct 687 ms ok 90 + select_distinct_on 75 ms ok 91 + select_implicit 151 ms ok 92 + select_having 85 ms ok 93 + subselect 1026 ms ok 94 + union 659 ms ok 95 + case 141 ms ok 96 + join 3643 ms ok 97 + aggregates 3321 ms ok 98 + transactions 327 ms ok 99 + random 121 ms ok 100 + portals 332 ms ok 101 + arrays 622 ms ok 102 + btree_index 4519 ms ok 103 + hash_index 1614 ms ok 104 + update 2357 ms ok 105 + delete 87 ms ok 106 + namespace 210 ms ok 107 + prepared_xacts 244 ms # parallel group (20 tests): init_privs drop_operator security_label password lock tablesample object_address replica_identity collate matview identity groupingsets generated spgist rowsecurity gist gin join_hash brin privileges ok 108 + brin 6948 ms ok 109 + gin 2826 ms ok 110 + gist 2290 ms ok 111 + spgist 2185 ms ok 112 + privileges 7378 ms ok 113 + init_privs 58 ms ok 114 + security_label 155 ms ok 115 + collate 996 ms ok 116 + matview 1373 ms ok 117 + lock 256 ms ok 118 + replica_identity 694 ms ok 119 + rowsecurity 2225 ms ok 120 + object_address 302 ms ok 121 + tablesample 284 ms ok 122 + groupingsets 2034 ms ok 123 + drop_operator 107 ms ok 124 + password 251 ms ok 125 + identity 1609 ms ok 126 + generated 2168 ms ok 127 + join_hash 6944 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 92 ms ok 129 + brin_multi 558 ms # parallel group (18 tests): collate.utf8 async dbsize tid tidscan tsrf alter_operator create_role sysviews misc_functions tidrangescan alter_generic without_overlaps incremental_sort create_table_like collate.icu.utf8 misc merge ok 130 + create_table_like 912 ms ok 131 + alter_generic 354 ms ok 132 + alter_operator 184 ms ok 133 + misc 1071 ms ok 134 + async 74 ms ok 135 + dbsize 88 ms ok 136 + merge 1082 ms ok 137 + misc_functions 296 ms not ok 138 + sysviews 252 ms ok 139 + tsrf 182 ms ok 140 + tid 143 ms ok 141 + tidscan 181 ms ok 142 + tidrangescan 341 ms ok 143 + collate.utf8 65 ms ok 144 + collate.icu.utf8 920 ms ok 145 + incremental_sort 700 ms ok 146 + create_role 190 ms ok 147 + without_overlaps 382 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 148 + rules 980 ms ok 149 + psql 1258 ms ok 150 + psql_crosstab 98 ms ok 151 + amutils 60 ms ok 152 + stats_ext 3874 ms ok 153 + collate.linux.utf8 54 ms ok 154 + collate.windows.win1252 43 ms ok 155 - select_parallel 8108 ms ok 156 - write_parallel 407 ms ok 157 - vacuum_parallel 420 ms # parallel group (2 tests): subscription publication ok 158 + publication 3431 ms ok 159 + subscription 129 ms # parallel group (17 tests): portals_p2 advisory_lock combocid xmlmap tsdicts functional_deps equivclass guc dependency select_views window bitmapops cluster indirect_toast foreign_data tsearch foreign_key ok 160 + select_views 830 ms ok 161 + portals_p2 133 ms ok 162 + foreign_key 3825 ms ok 163 + cluster 1563 ms ok 164 + dependency 541 ms ok 165 + guc 408 ms ok 166 + bitmapops 1557 ms ok 167 + combocid 161 ms ok 168 + tsearch 3356 ms ok 169 + tsdicts 324 ms ok 170 + foreign_data 2828 ms ok 171 + window 1541 ms ok 172 + xmlmap 306 ms ok 173 + functional_deps 333 ms ok 174 + advisory_lock 160 ms ok 175 + indirect_toast 1768 ms ok 176 + equivclass 375 ms # parallel group (8 tests): json_encoding jsonpath_encoding jsonpath sqljson sqljson_queryfuncs jsonb_jsonpath json jsonb ok 177 + json 532 ms ok 178 + jsonb 1085 ms ok 179 + json_encoding 39 ms ok 180 + jsonpath 114 ms ok 181 + jsonpath_encoding 41 ms ok 182 + jsonb_jsonpath 473 ms ok 183 + sqljson 247 ms ok 184 + sqljson_queryfuncs 426 ms # parallel group (18 tests): prepare returning plancache limit conversion temp copy2 sequence polymorphism truncate rowtypes largeobject with domain rangefuncs xml plpgsql alter_table ok 185 + plancache 441 ms ok 186 + limit 535 ms ok 187 + plpgsql 5163 ms ok 188 + copy2 746 ms ok 189 + temp 660 ms ok 190 + domain 1384 ms ok 191 + rangefuncs 1393 ms ok 192 + prepare 173 ms ok 193 + conversion 554 ms ok 194 + truncate 967 ms ok 195 + alter_table 5804 ms ok 196 + sequence 821 ms ok 197 + polymorphism 908 ms ok 198 + rowtypes 1120 ms ok 199 + returning 311 ms ok 200 + largeobject 1135 ms ok 201 + with 1227 ms ok 202 + xml 3885 ms # parallel group (13 tests): hash_part reloptions explain partition_info predicate compression memoize stats partition_aggregate tuplesort partition_join indexing partition_prune ok 203 + partition_join 2599 ms ok 204 + partition_prune 2829 ms ok 205 + reloptions 143 ms ok 206 + hash_part 104 ms ok 207 + indexing 2789 ms ok 208 + partition_aggregate 1845 ms ok 209 + partition_info 262 ms ok 210 + tuplesort 2157 ms ok 211 + explain 243 ms ok 212 + compression 590 ms ok 213 + memoize 755 ms ok 214 + stats 1551 ms ok 215 + predicate 263 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 486 ms ok 217 + event_trigger 560 ms ok 218 - event_trigger_login 84 ms ok 219 - fast_default 212 ms ok 220 - tablespace 691 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/sysviews.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out 2024-03-21 08:25:34.250359703 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-21 08:29:50.314343560 +0000 @@ -134,7 +134,8 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) + enable_toast_cache | off +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [08:30:23.551](57.658s) not ok 5 - regression tests pass [08:30:23.551](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [08:30:23.551](0.000s) # got: '256' # expected: '0' # Checking port 51994 # Found port 51994 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=51994 host=/tmp/0tOIvQXIej Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [08:30:23.554](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: C.UTF-8 LC_CTYPE: C.UTF-8 LC_MESSAGES: C LC_MONETARY: C.UTF-8 LC_NUMERIC: C.UTF-8 LC_TIME: C.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 ... Etc/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=51993 host=/tmp/0tOIvQXIej dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_T7rR/dump1.sql [08:30:28.592](5.038s) 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/0tOIvQXIej -p 51993 -P 51994 --copy --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:30:29.234](0.643s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [08:30:29.235](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/0tOIvQXIej -p 51993 -P 51994 --copy --check [08:30:30.388](1.154s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [08:30:30.389](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [08:30:30.389](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 40141 ### 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/0tOIvQXIej -p 51993 -P 51994 --copy --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:30:33.366](2.977s) ok 12 - run of pg_upgrade --check for new instance [08:30:33.366](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/0tOIvQXIej -p 51993 -P 51994 --copy 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 Copying 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:30:49.541](16.175s) ok 14 - run of pg_upgrade for new instance [08:30:49.541](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 43843 [08:30:49.693](0.151s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=51994 host=/tmp/0tOIvQXIej dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_T7rR/dump2.sql [08:30:52.332](2.639s) ok 17 - dump after running pg_upgrade [08:30:52.400](0.069s) ok 18 - old and new dumps match after pg_upgrade [08:30:52.401](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:30:52.505](0.104s) # Looks like you failed 1 test of 18.