[02:46:50.310](0.028s) # testing using transfer mode --copy # Checking port 60422 # Found port 60422 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=60422 host=/tmp/FI10Jees5f Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [02:46:50.320](0.010s) # 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 22455 [02:46:51.726](1.406s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [02:46:51.800](0.074s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [02:46:51.958](0.158s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [02:46:52.277](0.320s) ok 4 - created database with ASCII characters from 91 to 127 [02:46:52.278](0.001s) # running regression tests in old instance # using postmaster on /tmp/FI10Jees5f, port 60422 ok 1 - test_setup 447 ms # parallel group (20 tests): varchar int4 oid pg_lsn char txid text int2 regproc name uuid float4 int8 money float8 enum bit boolean numeric rangetypes ok 2 + boolean 502 ms ok 3 + char 126 ms ok 4 + name 164 ms ok 5 + varchar 105 ms ok 6 + text 137 ms ok 7 + int2 151 ms ok 8 + int4 112 ms ok 9 + int8 191 ms ok 10 + oid 114 ms ok 11 + float4 175 ms ok 12 + float8 226 ms ok 13 + bit 388 ms ok 14 + numeric 1078 ms ok 15 + txid 135 ms ok 16 + uuid 174 ms ok 17 + enum 225 ms ok 18 + money 191 ms ok 19 + rangetypes 1316 ms ok 20 + pg_lsn 113 ms ok 21 + regproc 150 ms # parallel group (20 tests): circle lseg md5 path line macaddr numerology timetz time macaddr8 inet date point interval timestamp strings timestamptz polygon multirangetypes box ok 22 + strings 520 ms ok 23 + md5 83 ms ok 24 + numerology 168 ms ok 25 + point 348 ms ok 26 + lseg 70 ms ok 27 + line 108 ms ok 28 + box 1029 ms ok 29 + path 100 ms ok 30 + polygon 737 ms ok 31 + circle 66 ms ok 32 + date 262 ms ok 33 + time 174 ms ok 34 + timetz 172 ms ok 35 + timestamp 497 ms ok 36 + timestamptz 544 ms ok 37 + interval 421 ms ok 38 + inet 257 ms ok 39 + macaddr 138 ms ok 40 + macaddr8 196 ms ok 41 + multirangetypes 955 ms # parallel group (12 tests): comments misc_sanity unicode xid tstypes expressions mvcc geometry type_sanity horology regex opr_sanity ok 42 + geometry 384 ms ok 43 + horology 423 ms ok 44 + tstypes 182 ms ok 45 + regex 603 ms ok 46 + type_sanity 387 ms ok 47 + opr_sanity 870 ms ok 48 + misc_sanity 62 ms ok 49 + comments 52 ms ok 50 + expressions 188 ms ok 51 + unicode 115 ms ok 52 + xid 133 ms ok 53 + mvcc 191 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 332 ms ok 55 + copyselect 35 ms ok 56 + copydml 123 ms ok 57 + insert 948 ms ok 58 + insert_conflict 546 ms # parallel group (7 tests): create_function_c create_operator create_type create_misc create_schema create_procedure create_table ok 59 + create_function_c 35 ms ok 60 + create_misc 135 ms ok 61 + create_operator 84 ms ok 62 + create_procedure 214 ms ok 63 + create_table 1070 ms ok 64 + create_type 102 ms ok 65 + create_schema 170 ms # parallel group (5 tests): index_including index_including_gist create_view create_index_spgist create_index ok 66 + create_index 2064 ms ok 67 + create_index_spgist 1841 ms ok 68 + create_view 879 ms ok 69 + index_including 544 ms ok 70 + index_including_gist 791 ms # parallel group (16 tests): create_cast errors hash_func roleattributes create_aggregate drop_if_exists create_function_sql typed_table create_am select infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 159 ms ok 72 + create_function_sql 307 ms ok 73 + create_cast 80 ms ok 74 + constraints 1201 ms ok 75 + triggers 4174 ms ok 76 + select 406 ms ok 77 + inherit 2923 ms ok 78 + typed_table 330 ms ok 79 + vacuum 863 ms ok 80 + drop_if_exists 166 ms ok 81 + updatable_views 1866 ms ok 82 + roleattributes 133 ms ok 83 + create_am 399 ms ok 84 + hash_func 119 ms ok 85 + errors 96 ms ok 86 + infinite_recurse 698 ms ok 87 - sanity_check 367 ms # parallel group (20 tests): select_having select_distinct_on delete case select_implicit select_into namespace prepared_xacts random transactions portals union select_distinct arrays subselect hash_index update join aggregates btree_index ok 88 + select_into 325 ms ok 89 + select_distinct 1134 ms ok 90 + select_distinct_on 140 ms ok 91 + select_implicit 280 ms ok 92 + select_having 138 ms ok 93 + subselect 1411 ms ok 94 + union 938 ms ok 95 + case 279 ms ok 96 + join 3268 ms ok 97 + aggregates 3460 ms ok 98 + transactions 604 ms ok 99 + random 479 ms ok 100 + portals 757 ms ok 101 + arrays 1216 ms ok 102 + btree_index 3945 ms ok 103 + hash_index 2244 ms ok 104 + update 2442 ms ok 105 + delete 157 ms ok 106 + namespace 327 ms ok 107 + prepared_xacts 370 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample lock password object_address replica_identity collate identity matview brin groupingsets spgist generated rowsecurity gin gist join_hash privileges ok 108 + brin 1738 ms ok 109 + gin 2414 ms ok 110 + gist 2496 ms ok 111 + spgist 2097 ms ok 112 + privileges 7089 ms ok 113 + init_privs 67 ms ok 114 + security_label 185 ms ok 115 + collate 974 ms ok 116 + matview 1347 ms ok 117 + lock 327 ms ok 118 + replica_identity 650 ms ok 119 + rowsecurity 2194 ms ok 120 + object_address 400 ms ok 121 + tablesample 269 ms ok 122 + groupingsets 1961 ms ok 123 + drop_operator 104 ms ok 124 + password 329 ms ok 125 + identity 1269 ms ok 126 + generated 2163 ms ok 127 + join_hash 6659 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 133 ms ok 129 + brin_multi 782 ms # parallel group (18 tests): async dbsize collate.utf8 tsrf tid alter_operator create_role tidscan tidrangescan sysviews misc_functions alter_generic incremental_sort create_table_like misc merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 855 ms ok 131 + alter_generic 404 ms ok 132 + alter_operator 181 ms ok 133 + misc 983 ms ok 134 + async 72 ms ok 135 + dbsize 87 ms ok 136 + merge 1040 ms ok 137 + misc_functions 354 ms not ok 138 + sysviews 328 ms ok 139 + tsrf 174 ms ok 140 + tid 177 ms ok 141 + tidscan 244 ms ok 142 + tidrangescan 264 ms ok 143 + collate.utf8 95 ms ok 144 + collate.icu.utf8 1237 ms ok 145 + incremental_sort 701 ms ok 146 + create_role 242 ms ok 147 + without_overlaps 1296 ms # parallel group (7 tests): collate.linux.utf8 amutils collate.windows.win1252 psql_crosstab psql rules stats_ext ok 148 + rules 979 ms ok 149 + psql 920 ms ok 150 + psql_crosstab 88 ms ok 151 + amutils 55 ms ok 152 + stats_ext 3624 ms ok 153 + collate.linux.utf8 33 ms ok 154 + collate.windows.win1252 57 ms ok 155 - select_parallel 8702 ms ok 156 - write_parallel 291 ms ok 157 - vacuum_parallel 554 ms # parallel group (2 tests): subscription publication ok 158 + publication 2965 ms ok 159 + subscription 227 ms # parallel group (17 tests): portals_p2 advisory_lock combocid tsdicts xmlmap functional_deps guc equivclass dependency select_views window bitmapops cluster indirect_toast foreign_data tsearch foreign_key ok 160 + select_views 766 ms ok 161 + portals_p2 230 ms ok 162 + foreign_key 4767 ms ok 163 + cluster 1777 ms ok 164 + dependency 589 ms ok 165 + guc 429 ms ok 166 + bitmapops 1566 ms ok 167 + combocid 319 ms ok 168 + tsearch 3451 ms ok 169 + tsdicts 371 ms ok 170 + foreign_data 3385 ms ok 171 + window 1477 ms ok 172 + xmlmap 376 ms ok 173 + functional_deps 379 ms ok 174 + advisory_lock 261 ms ok 175 + indirect_toast 1836 ms ok 176 + equivclass 433 ms # parallel group (8 tests): json_encoding jsonpath jsonpath_encoding sqljson_queryfuncs sqljson json jsonb_jsonpath jsonb ok 177 + json 361 ms ok 178 + jsonb 632 ms ok 179 + json_encoding 79 ms ok 180 + jsonpath 84 ms ok 181 + jsonpath_encoding 90 ms ok 182 + jsonb_jsonpath 417 ms ok 183 + sqljson 263 ms ok 184 + sqljson_queryfuncs 247 ms # parallel group (18 tests): prepare returning limit plancache conversion temp sequence copy2 truncate polymorphism rowtypes largeobject with domain rangefuncs xml plpgsql alter_table ok 185 + plancache 401 ms ok 186 + limit 383 ms ok 187 + plpgsql 5604 ms ok 188 + copy2 689 ms ok 189 + temp 513 ms ok 190 + domain 1550 ms ok 191 + rangefuncs 1852 ms ok 192 + prepare 149 ms ok 193 + conversion 426 ms ok 194 + truncate 781 ms ok 195 + alter_table 6064 ms ok 196 + sequence 522 ms ok 197 + polymorphism 871 ms ok 198 + rowtypes 1201 ms ok 199 + returning 213 ms ok 200 + largeobject 1302 ms ok 201 + with 1392 ms ok 202 + xml 2860 ms # parallel group (13 tests): hash_part reloptions explain partition_info predicate compression memoize stats partition_aggregate partition_join tuplesort indexing partition_prune ok 203 + partition_join 2651 ms ok 204 + partition_prune 3065 ms ok 205 + reloptions 231 ms ok 206 + hash_part 177 ms ok 207 + indexing 2761 ms ok 208 + partition_aggregate 2196 ms ok 209 + partition_info 294 ms ok 210 + tuplesort 2749 ms ok 211 + explain 236 ms ok 212 + compression 771 ms ok 213 + memoize 922 ms ok 214 + stats 1670 ms ok 215 + predicate 327 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 445 ms ok 217 + event_trigger 502 ms ok 218 - event_trigger_login 85 ms ok 219 - fast_default 264 ms ok 220 - tablespace 692 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-31 02:43:44.438112493 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-31 02:47:18.129972953 +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 === [02:47:52.187](59.909s) not ok 5 - regression tests pass [02:47:52.187](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [02:47:52.188](0.000s) # got: '256' # expected: '0' # Checking port 60423 # Found port 60423 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=60423 host=/tmp/FI10Jees5f Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [02:47:52.195](0.008s) # 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=60422 host=/tmp/FI10Jees5f dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_taOa/dump1.sql [02:47:57.068](4.873s) 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/FI10Jees5f -p 60422 -P 60423 --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 [02:47:57.319](0.251s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [02:47:57.320](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/FI10Jees5f -p 60422 -P 60423 --copy --check [02:47:58.323](1.004s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [02:47:58.324](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [02:47:58.324](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 35963 ### 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/FI10Jees5f -p 60422 -P 60423 --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* [02:48:01.307](2.984s) ok 12 - run of pg_upgrade --check for new instance [02:48:01.308](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/FI10Jees5f -p 60422 -P 60423 --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 [02:48:18.488](17.181s) ok 14 - run of pg_upgrade for new instance [02:48:18.488](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 39874 [02:48:18.656](0.168s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=60423 host=/tmp/FI10Jees5f dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_taOa/dump2.sql [02:48:21.798](3.142s) ok 17 - dump after running pg_upgrade [02:48:21.888](0.090s) ok 18 - old and new dumps match after pg_upgrade [02:48:21.889](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" [02:48:21.994](0.105s) # Looks like you failed 1 test of 18.