[01:24:55.036](0.011s) # testing using transfer mode --clone # Checking port 51852 # Found port 51852 Name: old_node Data directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata Backup directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/backup Archive directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/archives Connection string: port=51852 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [01:24:55.069](0.033s) # initializing database system by running initdb # Running: initdb -D /Users/admin/pgsql/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 "admin". 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 /Users/admin/pgsql/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 /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l logfile start # Running: /Users/admin/pgsql/build/src/test/regress/pg_regress --config-auth /Users/admin/pgsql/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 /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /Users/admin/pgsql/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 11026 [01:24:57.005](1.936s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [01:24:57.202](0.197s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [01:24:57.287](0.085s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [01:24:57.632](0.346s) ok 4 - created database with ASCII characters from 91 to 127 [01:24:57.633](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f, port 51852 ok 1 - test_setup 369 ms # parallel group (20 tests): char uuid pg_lsn bit enum varchar oid name int2 txid boolean regproc int4 text money float4 float8 int8 rangetypes numeric ok 2 + boolean 296 ms ok 3 + char 131 ms ok 4 + name 275 ms ok 5 + varchar 263 ms ok 6 + text 295 ms ok 7 + int2 271 ms ok 8 + int4 287 ms ok 9 + int8 297 ms ok 10 + oid 253 ms ok 11 + float4 283 ms ok 12 + float8 284 ms ok 13 + bit 230 ms ok 14 + numeric 723 ms ok 15 + txid 247 ms ok 16 + uuid 206 ms ok 17 + enum 216 ms ok 18 + money 254 ms ok 19 + rangetypes 588 ms ok 20 + pg_lsn 194 ms ok 21 + regproc 228 ms # parallel group (20 tests): md5 strings lseg path circle interval line point time macaddr8 macaddr inet timetz numerology date polygon box timestamp timestamptz multirangetypes ok 22 + strings 204 ms ok 23 + md5 126 ms ok 24 + numerology 281 ms ok 25 + point 261 ms ok 26 + lseg 225 ms ok 27 + line 256 ms ok 28 + box 511 ms ok 29 + path 223 ms ok 30 + polygon 473 ms ok 31 + circle 228 ms ok 32 + date 274 ms ok 33 + time 236 ms ok 34 + timetz 245 ms ok 35 + timestamp 529 ms ok 36 + timestamptz 569 ms ok 37 + interval 210 ms ok 38 + inet 222 ms ok 39 + macaddr 215 ms ok 40 + macaddr8 208 ms ok 41 + multirangetypes 552 ms # parallel group (12 tests): misc_sanity comments unicode mvcc xid expressions type_sanity tstypes geometry horology opr_sanity regex ok 42 + geometry 175 ms ok 43 + horology 184 ms ok 44 + tstypes 170 ms ok 45 + regex 457 ms ok 46 + type_sanity 151 ms ok 47 + opr_sanity 388 ms ok 48 + misc_sanity 69 ms ok 49 + comments 66 ms ok 50 + expressions 130 ms ok 51 + unicode 67 ms ok 52 + xid 111 ms ok 53 + mvcc 81 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 184 ms ok 55 + copyselect 111 ms ok 56 + copydml 145 ms ok 57 + insert 831 ms ok 58 + insert_conflict 484 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_misc create_procedure create_table ok 59 + create_function_c 32 ms ok 60 + create_misc 185 ms ok 61 + create_operator 68 ms ok 62 + create_procedure 184 ms ok 63 + create_table 476 ms ok 64 + create_type 82 ms ok 65 + create_schema 78 ms # parallel group (5 tests): index_including_gist create_index_spgist index_including create_view create_index ok 66 + create_index 2404 ms ok 67 + create_index_spgist 526 ms ok 68 + create_view 892 ms ok 69 + index_including 771 ms ok 70 + index_including_gist 485 ms # parallel group (16 tests): create_cast create_aggregate hash_func errors roleattributes select typed_table drop_if_exists create_function_sql infinite_recurse create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 147 ms ok 72 + create_function_sql 309 ms ok 73 + create_cast 92 ms ok 74 + constraints 747 ms ok 75 + triggers 2146 ms ok 76 + select 170 ms ok 77 + inherit 1269 ms ok 78 + typed_table 205 ms ok 79 + vacuum 521 ms ok 80 + drop_if_exists 209 ms ok 81 + updatable_views 1138 ms ok 82 + roleattributes 144 ms ok 83 + create_am 428 ms ok 84 + hash_func 130 ms ok 85 + errors 130 ms ok 86 + infinite_recurse 320 ms ok 87 - sanity_check 82 ms # parallel group (20 tests): random delete namespace prepared_xacts select_distinct_on select_having select_implicit select_into case select_distinct union subselect portals transactions arrays update aggregates hash_index join btree_index ok 88 + select_into 208 ms ok 89 + select_distinct 230 ms ok 90 + select_distinct_on 172 ms ok 91 + select_implicit 187 ms ok 92 + select_having 180 ms ok 93 + subselect 265 ms ok 94 + union 222 ms ok 95 + case 205 ms ok 96 + join 1657 ms ok 97 + aggregates 1273 ms ok 98 + transactions 472 ms ok 99 + random 69 ms ok 100 + portals 434 ms ok 101 + arrays 662 ms ok 102 + btree_index 1904 ms ok 103 + hash_index 1575 ms ok 104 + update 954 ms ok 105 + delete 68 ms ok 106 + namespace 93 ms ok 107 + prepared_xacts 92 ms # parallel group (20 tests): init_privs drop_operator tablesample lock security_label collate password object_address groupingsets replica_identity spgist identity matview generated gin gist rowsecurity join_hash brin privileges ok 108 + brin 2734 ms ok 109 + gin 2192 ms ok 110 + gist 2198 ms ok 111 + spgist 1445 ms ok 112 + privileges 3183 ms ok 113 + init_privs 162 ms ok 114 + security_label 225 ms ok 115 + collate 328 ms ok 116 + matview 1748 ms ok 117 + lock 87 ms ok 118 + replica_identity 1093 ms ok 119 + rowsecurity 2179 ms ok 120 + object_address 594 ms ok 121 + tablesample 81 ms ok 122 + groupingsets 932 ms ok 123 + drop_operator 45 ms ok 124 + password 422 ms ok 125 + identity 1391 ms ok 126 + generated 1822 ms ok 127 + join_hash 2556 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 92 ms ok 129 + brin_multi 314 ms # parallel group (18 tests): async dbsize tsrf alter_operator alter_generic tid misc_functions merge sysviews collate.utf8 tidrangescan tidscan create_table_like create_role misc incremental_sort collate.icu.utf8 without_overlaps ok 130 + create_table_like 358 ms ok 131 + alter_generic 219 ms ok 132 + alter_operator 192 ms ok 133 + misc 548 ms ok 134 + async 142 ms ok 135 + dbsize 164 ms ok 136 + merge 284 ms ok 137 + misc_functions 250 ms not ok 138 + sysviews 310 ms ok 139 + tsrf 163 ms ok 140 + tid 199 ms ok 141 + tidscan 313 ms ok 142 + tidrangescan 308 ms ok 143 + collate.utf8 299 ms ok 144 + collate.icu.utf8 735 ms ok 145 + incremental_sort 524 ms ok 146 + create_role 346 ms ok 147 + without_overlaps 969 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1151 ms ok 149 + psql 815 ms ok 150 + psql_crosstab 69 ms ok 151 + amutils 51 ms ok 152 + stats_ext 1465 ms ok 153 + collate.linux.utf8 41 ms ok 154 + collate.windows.win1252 40 ms ok 155 - select_parallel 617 ms ok 156 - write_parallel 121 ms ok 157 - vacuum_parallel 87 ms # parallel group (2 tests): subscription publication ok 158 + publication 276 ms ok 159 + subscription 69 ms # parallel group (17 tests): portals_p2 advisory_lock functional_deps xmlmap combocid select_views dependency equivclass guc tsdicts bitmapops window indirect_toast tsearch cluster foreign_data foreign_key ok 160 + select_views 222 ms ok 161 + portals_p2 174 ms ok 162 + foreign_key 2253 ms ok 163 + cluster 568 ms ok 164 + dependency 224 ms ok 165 + guc 253 ms ok 166 + bitmapops 411 ms ok 167 + combocid 207 ms ok 168 + tsearch 548 ms ok 169 + tsdicts 240 ms ok 170 + foreign_data 848 ms ok 171 + window 408 ms ok 172 + xmlmap 177 ms ok 173 + functional_deps 169 ms ok 174 + advisory_lock 151 ms ok 175 + indirect_toast 424 ms ok 176 + equivclass 186 ms # parallel group (8 tests): jsonpath_encoding json_encoding jsonpath sqljson json sqljson_queryfuncs jsonb_jsonpath jsonb ok 177 + json 186 ms ok 178 + jsonb 352 ms ok 179 + json_encoding 64 ms ok 180 + jsonpath 140 ms ok 181 + jsonpath_encoding 56 ms ok 182 + jsonb_jsonpath 213 ms ok 183 + sqljson 137 ms ok 184 + sqljson_queryfuncs 186 ms # parallel group (18 tests): prepare returning limit plancache temp sequence conversion copy2 domain polymorphism truncate with rowtypes largeobject rangefuncs plpgsql xml alter_table ok 185 + plancache 369 ms ok 186 + limit 265 ms ok 187 + plpgsql 1496 ms ok 188 + copy2 415 ms ok 189 + temp 363 ms ok 190 + domain 420 ms ok 191 + rangefuncs 668 ms ok 192 + prepare 131 ms ok 193 + conversion 374 ms ok 194 + truncate 539 ms ok 195 + alter_table 2612 ms ok 196 + sequence 360 ms ok 197 + polymorphism 408 ms ok 198 + rowtypes 557 ms ok 199 + returning 146 ms ok 200 + largeobject 563 ms ok 201 + with 528 ms ok 202 + xml 1933 ms # parallel group (13 tests): predicate hash_part explain partition_info reloptions memoize compression partition_aggregate tuplesort partition_prune stats partition_join indexing ok 203 + partition_join 1954 ms ok 204 + partition_prune 1850 ms ok 205 + reloptions 232 ms ok 206 + hash_part 96 ms ok 207 + indexing 2117 ms ok 208 + partition_aggregate 984 ms ok 209 + partition_info 135 ms ok 210 + tuplesort 1340 ms ok 211 + explain 117 ms ok 212 + compression 294 ms ok 213 + memoize 261 ms ok 214 + stats 1875 ms ok 215 + predicate 61 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 175 ms ok 217 + event_trigger 606 ms ok 218 - event_trigger_login 128 ms ok 219 - fast_default 398 ms ok 220 - tablespace 1488 ms 1..220 # 1 of 220 tests failed. # The differences that caused some tests to fail can be viewed in the file "/Users/admin/pgsql/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 "/Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /Users/admin/pgsql/src/test/regress/expected/sysviews.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /Users/admin/pgsql/src/test/regress/expected/sysviews.out 2024-03-27 01:21:39 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-27 01:25:13 @@ -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 === [01:25:28.961](31.328s) not ok 5 - regression tests pass [01:25:28.961](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [01:25:28.961](0.000s) # got: '256' # expected: '0' # Checking port 51853 # Found port 51853 Name: new_node Data directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata Backup directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/backup Archive directory: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/archives Connection string: port=51853 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [01:25:28.975](0.015s) # initializing database system by running initdb # Running: initdb -D /Users/admin/pgsql/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 "admin". 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 /Users/admin/pgsql/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 /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l logfile start # Running: /Users/admin/pgsql/build/src/test/regress/pg_regress --config-auth /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata # Running: pg_dumpall --no-sync -d port=51852 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_xut2/dump1.sql [01:25:33.467](4.492s) ok 6 - dump before running pg_upgrade ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /Users/admin/pgsql/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 /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin/does/not/exist/ -B /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -s /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f -p 51852 -P 51853 --clone --check check for "/Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin/does/not/exist" failed: No such file or directory Failure, exiting [01:25:34.217](0.750s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [01:25:34.218](0.000s) ok 8 - pg_upgrade_output.d/ not removed after pg_upgrade failure # Running: pg_upgrade --no-sync -d /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -B /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -s /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f -p 51852 -P 51853 --clone --check [01:25:35.830](1.612s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [01:25:35.830](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [01:25:35.830](0.000s) ok 11 - invalid database causes failure stderr /(?^:^$)/ ### Starting node "old_node" # Running: pg_ctl -w -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /Users/admin/pgsql/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 19572 ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /Users/admin/pgsql/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 /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -B /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -s /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f -p 51852 -P 51853 --clone --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* [01:25:37.814](1.984s) ok 12 - run of pg_upgrade --check for new instance [01:25:37.814](0.000s) ok 13 - pg_upgrade_output.d/ removed after pg_upgrade --check success # Running: pg_upgrade --no-sync -d /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -B /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin -s /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f -p 51852 -P 51853 --clone 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 Cloning 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: /Users/admin/pgsql/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 [01:25:55.662](17.848s) ok 14 - run of pg_upgrade for new instance [01:25:55.662](0.000s) ok 15 - pg_upgrade_output.d/ removed after pg_upgrade success ### Starting node "new_node" # Running: pg_ctl -w -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l /Users/admin/pgsql/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 22989 [01:25:55.827](0.164s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=51853 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/jA7V6pBu2f dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_xut2/dump2.sql [01:26:03.063](7.236s) ok 17 - dump after running pg_upgrade [01:26:03.281](0.218s) ok 18 - old and new dumps match after pg_upgrade [01:26:03.281](0.001s) 1..18 ### Stopping node "new_node" using mode immediate # Running: pg_ctl -D /Users/admin/pgsql/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" [01:26:03.395](0.114s) # Looks like you failed 1 test of 18.