[18:10:25.233](0.013s) # testing using transfer mode --link # Checking port 53418 # Found port 53418 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=53418 host=/tmp/H7pVGKagCG Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [18:10:25.256](0.022s) # 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 7915 [18:10:27.099](1.843s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [18:10:27.261](0.162s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [18:10:27.343](0.082s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [18:10:27.425](0.082s) ok 4 - created database with ASCII characters from 91 to 127 [18:10:27.427](0.002s) # running regression tests in old instance # using postmaster on /tmp/H7pVGKagCG, port 53418 ok 1 - test_setup 501 ms # parallel group (20 tests): varchar oid pg_lsn txid char name regproc text uuid int2 int4 float4 money boolean float8 int8 bit enum rangetypes numeric ok 2 + boolean 336 ms ok 3 + char 179 ms ok 4 + name 188 ms ok 5 + varchar 103 ms ok 6 + text 254 ms ok 7 + int2 289 ms ok 8 + int4 294 ms ok 9 + int8 422 ms ok 10 + oid 136 ms ok 11 + float4 326 ms ok 12 + float8 393 ms ok 13 + bit 436 ms ok 14 + numeric 1021 ms ok 15 + txid 170 ms ok 16 + uuid 267 ms ok 17 + enum 463 ms ok 18 + money 326 ms ok 19 + rangetypes 869 ms ok 20 + pg_lsn 141 ms ok 21 + regproc 246 ms # parallel group (20 tests): md5 lseg path macaddr circle line time timetz point inet macaddr8 numerology polygon box date interval timestamp strings timestamptz multirangetypes ok 22 + strings 617 ms ok 23 + md5 46 ms ok 24 + numerology 248 ms ok 25 + point 181 ms ok 26 + lseg 64 ms ok 27 + line 115 ms ok 28 + box 374 ms ok 29 + path 86 ms ok 30 + polygon 303 ms ok 31 + circle 96 ms ok 32 + date 428 ms ok 33 + time 134 ms ok 34 + timetz 153 ms ok 35 + timestamp 537 ms ok 36 + timestamptz 635 ms ok 37 + interval 533 ms ok 38 + inet 235 ms ok 39 + macaddr 92 ms ok 40 + macaddr8 245 ms ok 41 + multirangetypes 812 ms # parallel group (12 tests): misc_sanity comments unicode mvcc type_sanity expressions xid tstypes geometry regex horology opr_sanity ok 42 + geometry 373 ms ok 43 + horology 466 ms ok 44 + tstypes 343 ms ok 45 + regex 374 ms ok 46 + type_sanity 179 ms ok 47 + opr_sanity 472 ms ok 48 + misc_sanity 37 ms ok 49 + comments 48 ms ok 50 + expressions 202 ms ok 51 + unicode 51 ms ok 52 + xid 258 ms ok 53 + mvcc 148 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 252 ms ok 55 + copyselect 74 ms ok 56 + copydml 174 ms ok 57 + insert 1398 ms ok 58 + insert_conflict 633 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 25 ms ok 60 + create_misc 137 ms ok 61 + create_operator 119 ms ok 62 + create_procedure 177 ms ok 63 + create_table 1779 ms ok 64 + create_type 163 ms ok 65 + create_schema 113 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1953 ms ok 67 + create_index_spgist 827 ms ok 68 + create_view 1029 ms ok 69 + index_including 618 ms ok 70 + index_including_gist 569 ms # parallel group (16 tests): hash_func errors create_cast select create_aggregate infinite_recurse drop_if_exists roleattributes typed_table create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 431 ms ok 72 + create_function_sql 561 ms ok 73 + create_cast 228 ms ok 74 + constraints 1588 ms ok 75 + triggers 4905 ms ok 76 + select 409 ms ok 77 + inherit 3748 ms ok 78 + typed_table 559 ms ok 79 + vacuum 843 ms ok 80 + drop_if_exists 517 ms ok 81 + updatable_views 2319 ms ok 82 + roleattributes 525 ms ok 83 + create_am 566 ms ok 84 + hash_func 81 ms ok 85 + errors 126 ms ok 86 + infinite_recurse 449 ms ok 87 - sanity_check 204 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit namespace case select_into select_distinct prepared_xacts union portals hash_index transactions subselect arrays update aggregates btree_index join ok 88 + select_into 377 ms ok 89 + select_distinct 410 ms ok 90 + select_distinct_on 86 ms ok 91 + select_implicit 322 ms ok 92 + select_having 196 ms ok 93 + subselect 1086 ms ok 94 + union 759 ms ok 95 + case 369 ms ok 96 + join 2495 ms ok 97 + aggregates 2050 ms ok 98 + transactions 1055 ms ok 99 + random 268 ms ok 100 + portals 942 ms ok 101 + arrays 1124 ms ok 102 + btree_index 2246 ms ok 103 + hash_index 1041 ms ok 104 + update 1479 ms ok 105 + delete 122 ms ok 106 + namespace 362 ms ok 107 + prepared_xacts 479 ms # parallel group (20 tests): init_privs drop_operator password security_label tablesample object_address lock groupingsets collate spgist replica_identity gin gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 3942 ms ok 109 + gin 1624 ms ok 110 + gist 1851 ms ok 111 + spgist 1220 ms ok 112 + privileges 4473 ms ok 113 + init_privs 67 ms ok 114 + security_label 423 ms ok 115 + collate 1151 ms ok 116 + matview 2029 ms ok 117 + lock 803 ms ok 118 + replica_identity 1267 ms ok 119 + rowsecurity 4155 ms ok 120 + object_address 758 ms ok 121 + tablesample 589 ms ok 122 + groupingsets 1131 ms ok 123 + drop_operator 104 ms ok 124 + password 353 ms ok 125 + identity 2234 ms ok 126 + generated 3831 ms ok 127 + join_hash 3975 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 258 ms ok 129 + brin_multi 847 ms # parallel group (18 tests): async collate.utf8 sysviews tidrangescan tidscan dbsize tid alter_operator tsrf misc incremental_sort misc_functions create_role alter_generic merge create_table_like collate.icu.utf8 without_overlaps ok 130 + create_table_like 1095 ms ok 131 + alter_generic 721 ms ok 132 + alter_operator 212 ms ok 133 + misc 293 ms ok 134 + async 71 ms ok 135 + dbsize 176 ms ok 136 + merge 1070 ms ok 137 + misc_functions 349 ms not ok 138 + sysviews 147 ms ok 139 + tsrf 215 ms ok 140 + tid 184 ms ok 141 + tidscan 173 ms ok 142 + tidrangescan 166 ms ok 143 + collate.utf8 102 ms ok 144 + collate.icu.utf8 1126 ms ok 145 + incremental_sort 340 ms ok 146 + create_role 352 ms ok 147 + without_overlaps 1386 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 psql_crosstab amutils psql rules stats_ext ok 148 + rules 1347 ms ok 149 + psql 1341 ms ok 150 + psql_crosstab 43 ms ok 151 + amutils 51 ms ok 152 + stats_ext 3580 ms ok 153 + collate.linux.utf8 18 ms ok 154 + collate.windows.win1252 28 ms ok 155 - select_parallel 2065 ms ok 156 - write_parallel 147 ms ok 157 - vacuum_parallel 116 ms # parallel group (2 tests): subscription publication ok 158 + publication 1181 ms ok 159 + subscription 138 ms # parallel group (17 tests): portals_p2 xmlmap combocid advisory_lock bitmapops functional_deps equivclass select_views indirect_toast tsdicts dependency guc tsearch window cluster foreign_data foreign_key ok 160 + select_views 492 ms ok 161 + portals_p2 184 ms ok 162 + foreign_key 7352 ms ok 163 + cluster 1079 ms ok 164 + dependency 571 ms ok 165 + guc 606 ms ok 166 + bitmapops 372 ms ok 167 + combocid 329 ms ok 168 + tsearch 885 ms ok 169 + tsdicts 535 ms ok 170 + foreign_data 2973 ms ok 171 + window 926 ms ok 172 + xmlmap 242 ms ok 173 + functional_deps 433 ms ok 174 + advisory_lock 343 ms ok 175 + indirect_toast 512 ms ok 176 + equivclass 444 ms # parallel group (8 tests): json_encoding jsonpath_encoding jsonpath sqljson sqljson_queryfuncs jsonb_jsonpath json jsonb ok 177 + json 349 ms ok 178 + jsonb 703 ms ok 179 + json_encoding 41 ms ok 180 + jsonpath 126 ms ok 181 + jsonpath_encoding 52 ms ok 182 + jsonb_jsonpath 334 ms ok 183 + sqljson 206 ms ok 184 + sqljson_queryfuncs 280 ms # parallel group (18 tests): prepare returning conversion limit plancache temp rowtypes sequence xml with truncate largeobject copy2 polymorphism rangefuncs domain plpgsql alter_table ok 185 + plancache 429 ms ok 186 + limit 387 ms ok 187 + plpgsql 2609 ms ok 188 + copy2 1167 ms ok 189 + temp 714 ms ok 190 + domain 1459 ms ok 191 + rangefuncs 1228 ms ok 192 + prepare 153 ms ok 193 + conversion 336 ms ok 194 + truncate 1104 ms ok 195 + alter_table 11809 ms ok 196 + sequence 1067 ms ok 197 + polymorphism 1220 ms ok 198 + rowtypes 864 ms ok 199 + returning 298 ms ok 200 + largeobject 1158 ms ok 201 + with 1091 ms ok 202 + xml 1087 ms # parallel group (13 tests): predicate reloptions hash_part explain memoize partition_info compression partition_aggregate tuplesort stats partition_join partition_prune indexing ok 203 + partition_join 2715 ms ok 204 + partition_prune 4076 ms ok 205 + reloptions 109 ms ok 206 + hash_part 125 ms ok 207 + indexing 4876 ms ok 208 + partition_aggregate 1294 ms ok 209 + partition_info 378 ms ok 210 + tuplesort 1373 ms ok 211 + explain 270 ms ok 212 + compression 1099 ms ok 213 + memoize 296 ms ok 214 + stats 1574 ms ok 215 + predicate 56 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 366 ms ok 217 + event_trigger 533 ms ok 218 - event_trigger_login 123 ms ok 219 - fast_default 597 ms ok 220 - tablespace 1164 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-04-02 18:08:49.723950000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-04-02 18:10:49.231184000 +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 === [18:11:25.042](57.615s) not ok 5 - regression tests pass [18:11:25.042](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [18:11:25.042](0.000s) # got: '256' # expected: '0' # Checking port 53419 # Found port 53419 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=53419 host=/tmp/H7pVGKagCG Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [18:11:25.045](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=53418 host=/tmp/H7pVGKagCG dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_9QGa/dump1.sql [18:11:29.790](4.745s) 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/H7pVGKagCG -p 53418 -P 53419 --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 [18:11:30.055](0.265s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [18:11:30.055](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/H7pVGKagCG -p 53418 -P 53419 --link --check [18:11:31.331](1.276s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [18:11:31.333](0.002s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [18:11:31.335](0.002s) 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 20914 ### 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/H7pVGKagCG -p 53418 -P 53419 --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* [18:11:33.920](2.585s) ok 12 - run of pg_upgrade --check for new instance [18:11:33.922](0.002s) 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/H7pVGKagCG -p 53418 -P 53419 --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 [18:11:49.920](15.998s) ok 14 - run of pg_upgrade for new instance [18:11:49.920](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 23967 [18:11:50.057](0.137s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=53419 host=/tmp/H7pVGKagCG dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_9QGa/dump2.sql [18:11:52.250](2.193s) ok 17 - dump after running pg_upgrade [18:11:52.335](0.085s) ok 18 - old and new dumps match after pg_upgrade [18:11:52.335](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" [18:11:52.441](0.106s) # Looks like you failed 1 test of 18.