[23:26:58.709](0.007s) # testing using transfer mode --clone # Checking port 53465 # Found port 53465 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=53465 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/_npPhPR8w5 Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [23:26:58.729](0.020s) # 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 9858 [23:27:00.720](1.992s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [23:27:00.916](0.195s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [23:27:01.068](0.152s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [23:27:01.170](0.103s) ok 4 - created database with ASCII characters from 91 to 127 [23:27:01.171](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/_npPhPR8w5, port 53465 ok 1 - test_setup 390 ms # parallel group (20 tests): varchar char text name oid pg_lsn int2 txid float4 int4 uuid boolean money regproc int8 bit float8 enum rangetypes numeric ok 2 + boolean 153 ms ok 3 + char 106 ms ok 4 + name 115 ms ok 5 + varchar 98 ms ok 6 + text 110 ms ok 7 + int2 124 ms ok 8 + int4 132 ms ok 9 + int8 150 ms ok 10 + oid 106 ms ok 11 + float4 120 ms ok 12 + float8 143 ms ok 13 + bit 139 ms ok 14 + numeric 575 ms ok 15 + txid 97 ms ok 16 + uuid 105 ms ok 17 + enum 131 ms ok 18 + money 105 ms ok 19 + rangetypes 384 ms ok 20 + pg_lsn 74 ms ok 21 + regproc 94 ms # parallel group (20 tests): md5 lseg macaddr path line circle time point numerology timetz macaddr8 inet interval date polygon strings timestamp box timestamptz multirangetypes ok 22 + strings 470 ms ok 23 + md5 171 ms ok 24 + numerology 211 ms ok 25 + point 208 ms ok 26 + lseg 172 ms ok 27 + line 183 ms ok 28 + box 537 ms ok 29 + path 176 ms ok 30 + polygon 396 ms ok 31 + circle 165 ms ok 32 + date 236 ms ok 33 + time 162 ms ok 34 + timetz 182 ms ok 35 + timestamp 475 ms ok 36 + timestamptz 546 ms ok 37 + interval 209 ms ok 38 + inet 182 ms ok 39 + macaddr 134 ms ok 40 + macaddr8 168 ms ok 41 + multirangetypes 582 ms # parallel group (12 tests): comments misc_sanity unicode mvcc type_sanity expressions xid geometry tstypes horology opr_sanity regex ok 42 + geometry 177 ms ok 43 + horology 233 ms ok 44 + tstypes 169 ms ok 45 + regex 592 ms ok 46 + type_sanity 138 ms ok 47 + opr_sanity 486 ms ok 48 + misc_sanity 78 ms ok 49 + comments 74 ms ok 50 + expressions 131 ms ok 51 + unicode 85 ms ok 52 + xid 124 ms ok 53 + mvcc 82 ms # parallel group (5 tests): copyselect copydml insert_conflict copy insert ok 54 + copy 181 ms ok 55 + copyselect 52 ms ok 56 + copydml 58 ms ok 57 + insert 499 ms ok 58 + insert_conflict 143 ms # parallel group (7 tests): create_function_c create_operator create_schema create_misc create_type create_procedure create_table ok 59 + create_function_c 28 ms ok 60 + create_misc 69 ms ok 61 + create_operator 51 ms ok 62 + create_procedure 94 ms ok 63 + create_table 697 ms ok 64 + create_type 86 ms ok 65 + create_schema 50 ms # parallel group (5 tests): index_including create_index_spgist create_view index_including_gist create_index ok 66 + create_index 2516 ms ok 67 + create_index_spgist 479 ms ok 68 + create_view 543 ms ok 69 + index_including 430 ms ok 70 + index_including_gist 541 ms # parallel group (16 tests): create_cast hash_func roleattributes select errors drop_if_exists create_aggregate create_function_sql infinite_recurse typed_table create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 198 ms ok 72 + create_function_sql 235 ms ok 73 + create_cast 67 ms ok 74 + constraints 1019 ms ok 75 + triggers 2592 ms ok 76 + select 122 ms ok 77 + inherit 1857 ms ok 78 + typed_table 295 ms ok 79 + vacuum 554 ms ok 80 + drop_if_exists 165 ms ok 81 + updatable_views 1207 ms ok 82 + roleattributes 96 ms ok 83 + create_am 349 ms ok 84 + hash_func 69 ms ok 85 + errors 101 ms ok 86 + infinite_recurse 252 ms ok 87 - sanity_check 250 ms # parallel group (20 tests): select_distinct_on select_into select_having delete random select_implicit select_distinct case prepared_xacts namespace union transactions subselect portals arrays aggregates update btree_index join hash_index ok 88 + select_into 395 ms ok 89 + select_distinct 444 ms ok 90 + select_distinct_on 232 ms ok 91 + select_implicit 404 ms ok 92 + select_having 394 ms ok 93 + subselect 695 ms ok 94 + union 587 ms ok 95 + case 458 ms ok 96 + join 2609 ms ok 97 + aggregates 1826 ms ok 98 + transactions 662 ms ok 99 + random 373 ms ok 100 + portals 704 ms ok 101 + arrays 879 ms ok 102 + btree_index 2420 ms ok 103 + hash_index 2740 ms ok 104 + update 1921 ms ok 105 + delete 339 ms ok 106 + namespace 445 ms ok 107 + prepared_xacts 435 ms # parallel group (20 tests): init_privs drop_operator replica_identity security_label object_address tablesample lock collate password groupingsets identity matview spgist rowsecurity generated gin gist join_hash brin privileges ok 108 + brin 1996 ms ok 109 + gin 1295 ms ok 110 + gist 1330 ms ok 111 + spgist 1049 ms ok 112 + privileges 2486 ms ok 113 + init_privs 81 ms ok 114 + security_label 200 ms ok 115 + collate 317 ms ok 116 + matview 833 ms ok 117 + lock 309 ms ok 118 + replica_identity 152 ms ok 119 + rowsecurity 1057 ms ok 120 + object_address 234 ms ok 121 + tablesample 288 ms ok 122 + groupingsets 579 ms ok 123 + drop_operator 118 ms ok 124 + password 319 ms ok 125 + identity 572 ms ok 126 + generated 1063 ms ok 127 + join_hash 1931 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 49 ms ok 129 + brin_multi 509 ms # parallel group (18 tests): async dbsize tid tidscan collate.utf8 alter_operator tidrangescan tsrf incremental_sort create_role misc misc_functions alter_generic sysviews merge create_table_like collate.icu.utf8 without_overlaps ok 130 + create_table_like 758 ms ok 131 + alter_generic 404 ms ok 132 + alter_operator 237 ms ok 133 + misc 378 ms ok 134 + async 94 ms ok 135 + dbsize 147 ms ok 136 + merge 748 ms ok 137 + misc_functions 383 ms ok 138 + sysviews 398 ms ok 139 + tsrf 235 ms ok 140 + tid 152 ms ok 141 + tidscan 210 ms ok 142 + tidrangescan 215 ms ok 143 + collate.utf8 205 ms ok 144 + collate.icu.utf8 896 ms ok 145 + incremental_sort 242 ms ok 146 + create_role 240 ms ok 147 + without_overlaps 1037 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 402 ms ok 149 + psql 448 ms ok 150 + psql_crosstab 52 ms ok 151 + amutils 42 ms ok 152 + stats_ext 1167 ms ok 153 + collate.linux.utf8 33 ms ok 154 + collate.windows.win1252 31 ms ok 155 - select_parallel 723 ms ok 156 - write_parallel 82 ms ok 157 - vacuum_parallel 118 ms # parallel group (2 tests): subscription publication ok 158 + publication 703 ms ok 159 + subscription 84 ms # parallel group (17 tests): portals_p2 combocid guc advisory_lock tsdicts dependency xmlmap functional_deps equivclass indirect_toast select_views cluster window bitmapops tsearch foreign_data foreign_key ok 160 + select_views 732 ms ok 161 + portals_p2 134 ms ok 162 + foreign_key 1695 ms ok 163 + cluster 745 ms ok 164 + dependency 206 ms ok 165 + guc 172 ms ok 166 + bitmapops 871 ms ok 167 + combocid 167 ms ok 168 + tsearch 1007 ms ok 169 + tsdicts 163 ms ok 170 + foreign_data 1153 ms ok 171 + window 755 ms ok 172 + xmlmap 208 ms ok 173 + functional_deps 208 ms ok 174 + advisory_lock 144 ms ok 175 + indirect_toast 470 ms ok 176 + equivclass 278 ms # parallel group (9 tests): jsonpath_encoding json_encoding jsonpath jsonb_jsonpath sqljson sqljson_jsontable sqljson_queryfuncs json jsonb ok 177 + json 372 ms ok 178 + jsonb 459 ms ok 179 + json_encoding 119 ms ok 180 + jsonpath 177 ms ok 181 + jsonpath_encoding 103 ms ok 182 + jsonb_jsonpath 222 ms ok 183 + sqljson 298 ms ok 184 + sqljson_queryfuncs 321 ms ok 185 + sqljson_jsontable 294 ms # parallel group (18 tests): plancache limit temp prepare largeobject sequence truncate returning conversion domain with polymorphism rowtypes copy2 rangefuncs plpgsql xml alter_table ok 186 + plancache 164 ms ok 187 + limit 210 ms ok 188 + plpgsql 1471 ms ok 189 + copy2 839 ms ok 190 + temp 212 ms ok 191 + domain 681 ms ok 192 + rangefuncs 961 ms ok 193 + prepare 277 ms ok 194 + conversion 598 ms ok 195 + truncate 535 ms ok 196 + alter_table 3555 ms ok 197 + sequence 447 ms ok 198 + polymorphism 758 ms ok 199 + rowtypes 757 ms ok 200 + returning 527 ms ok 201 + largeobject 314 ms ok 202 + with 667 ms ok 203 + xml 2204 ms # parallel group (15 tests): predicate reloptions explain partition_info memoize hash_part compression partition_merge partition_aggregate partition_split tuplesort stats partition_prune indexing partition_join ok 204 + partition_merge 1348 ms ok 205 + partition_split 1564 ms not ok 206 + partition_join 2310 ms ok 207 + partition_prune 2111 ms ok 208 + reloptions 306 ms ok 209 + hash_part 580 ms ok 210 + indexing 2133 ms ok 211 + partition_aggregate 1485 ms ok 212 + partition_info 306 ms ok 213 + tuplesort 1773 ms ok 214 + explain 292 ms ok 215 + compression 1172 ms ok 216 + memoize 312 ms ok 217 + stats 1826 ms ok 218 + predicate 225 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 170 ms ok 220 + event_trigger 566 ms ok 221 - event_trigger_login 71 ms ok 222 - fast_default 602 ms ok 223 - tablespace 864 ms 1..223 # 1 of 223 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/partition_join.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out --- /Users/admin/pgsql/src/test/regress/expected/partition_join.out 2024-04-25 23:24:34 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out 2024-04-25 23:27:31 @@ -5133,17 +5133,15 @@ QUERY PLAN ----------------------------------------------------------------------- Limit - -> Merge Append - Sort Key: x.id - -> Merge Left Join - Merge Cond: (x_1.id = y_1.id) + -> Merge Left Join + Merge Cond: (x.id = y.id) + -> Append -> Index Only Scan using fract_t0_pkey on fract_t0 x_1 - -> Index Only Scan using fract_t0_pkey on fract_t0 y_1 - -> Merge Left Join - Merge Cond: (x_2.id = y_2.id) -> Index Only Scan using fract_t1_pkey on fract_t1 x_2 + -> Append + -> Index Only Scan using fract_t0_pkey on fract_t0 y_1 -> Index Only Scan using fract_t1_pkey on fract_t1 y_2 -(11 rows) +(9 rows) EXPLAIN (COSTS OFF) SELECT x.id, y.id FROM fract_t x LEFT JOIN fract_t y USING (id) ORDER BY x.id DESC LIMIT 10; === EOF === [23:27:34.260](33.089s) not ok 5 - regression tests pass [23:27:34.260](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [23:27:34.260](0.000s) # got: '256' # expected: '0' # Checking port 53466 # Found port 53466 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=53466 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/_npPhPR8w5 Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [23:27:34.268](0.007s) # 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=53465 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/_npPhPR8w5 dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_OlXC/dump1.sql [23:27:38.278](4.010s) 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/_npPhPR8w5 -p 53465 -P 53466 --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 [23:27:38.713](0.435s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [23:27:38.713](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/_npPhPR8w5 -p 53465 -P 53466 --clone --check [23:27:41.384](2.671s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [23:27:41.385](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [23:27:41.385](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 18734 ### 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/_npPhPR8w5 -p 53465 -P 53466 --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* [23:27:43.265](1.880s) ok 12 - run of pg_upgrade --check for new instance [23:27:43.265](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/_npPhPR8w5 -p 53465 -P 53466 --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 [23:28:01.175](17.910s) ok 14 - run of pg_upgrade for new instance [23:28:01.175](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 22268 [23:28:01.458](0.283s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=53466 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/_npPhPR8w5 dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_OlXC/dump2.sql [23:28:05.966](4.508s) ok 17 - dump after running pg_upgrade [23:28:06.059](0.093s) ok 18 - old and new dumps match after pg_upgrade [23:28:06.059](0.000s) 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" [23:28:06.172](0.113s) # Looks like you failed 1 test of 18.