[18:11:32.782](0.008s) # testing using transfer mode --clone # Checking port 63545 # Found port 63545 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=63545 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/DDVqyow89E Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [18:11:32.802](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 9688 [18:11:34.656](1.854s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [18:11:35.143](0.487s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [18:11:35.589](0.446s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [18:11:35.757](0.168s) ok 4 - created database with ASCII characters from 91 to 127 [18:11:35.757](0.001s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/DDVqyow89E, port 63545 ok 1 - test_setup 556 ms # parallel group (20 tests): varchar int2 text char name oid int4 boolean pg_lsn txid float4 int8 money uuid float8 regproc bit enum numeric rangetypes ok 2 + boolean 462 ms ok 3 + char 199 ms ok 4 + name 196 ms ok 5 + varchar 156 ms ok 6 + text 189 ms ok 7 + int2 183 ms ok 8 + int4 374 ms ok 9 + int8 544 ms ok 10 + oid 298 ms ok 11 + float4 530 ms ok 12 + float8 544 ms ok 13 + bit 659 ms ok 14 + numeric 1175 ms ok 15 + txid 513 ms ok 16 + uuid 526 ms ok 17 + enum 647 ms ok 18 + money 500 ms ok 19 + rangetypes 1303 ms ok 20 + pg_lsn 483 ms ok 21 + regproc 520 ms # parallel group (20 tests): md5 lseg path circle line point time macaddr macaddr8 inet date numerology timetz strings polygon interval box timestamptz timestamp multirangetypes ok 22 + strings 339 ms ok 23 + md5 91 ms ok 24 + numerology 303 ms ok 25 + point 116 ms ok 26 + lseg 92 ms ok 27 + line 108 ms ok 28 + box 582 ms ok 29 + path 96 ms ok 30 + polygon 414 ms ok 31 + circle 91 ms ok 32 + date 256 ms ok 33 + time 94 ms ok 34 + timetz 297 ms ok 35 + timestamp 663 ms ok 36 + timestamptz 619 ms ok 37 + interval 392 ms ok 38 + inet 195 ms ok 39 + macaddr 125 ms ok 40 + macaddr8 188 ms ok 41 + multirangetypes 726 ms # parallel group (12 tests): misc_sanity comments unicode mvcc tstypes xid expressions geometry type_sanity horology opr_sanity regex ok 42 + geometry 213 ms ok 43 + horology 255 ms ok 44 + tstypes 163 ms ok 45 + regex 474 ms ok 46 + type_sanity 215 ms ok 47 + opr_sanity 393 ms ok 48 + misc_sanity 76 ms ok 49 + comments 75 ms ok 50 + expressions 202 ms ok 51 + unicode 73 ms ok 52 + xid 169 ms ok 53 + mvcc 80 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 250 ms ok 55 + copyselect 161 ms ok 56 + copydml 158 ms ok 57 + insert 1311 ms ok 58 + insert_conflict 723 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 156 ms ok 60 + create_misc 527 ms ok 61 + create_operator 518 ms ok 62 + create_procedure 564 ms ok 63 + create_table 1357 ms ok 64 + create_type 536 ms ok 65 + create_schema 452 ms # parallel group (5 tests): create_index_spgist index_including_gist index_including create_view create_index ok 66 + create_index 4861 ms ok 67 + create_index_spgist 1372 ms ok 68 + create_view 2642 ms ok 69 + index_including 2633 ms ok 70 + index_including_gist 1505 ms # parallel group (16 tests): errors hash_func create_am infinite_recurse create_cast select create_aggregate drop_if_exists roleattributes create_function_sql typed_table vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 280 ms ok 72 + create_function_sql 524 ms ok 73 + create_cast 262 ms ok 74 + constraints 2554 ms ok 75 + triggers 3744 ms ok 76 + select 266 ms ok 77 + inherit 3546 ms ok 78 + typed_table 515 ms ok 79 + vacuum 1154 ms ok 80 + drop_if_exists 261 ms ok 81 + updatable_views 3102 ms ok 82 + roleattributes 255 ms ok 83 + create_am 84 ms ok 84 + hash_func 48 ms ok 85 + errors 45 ms ok 86 + infinite_recurse 185 ms ok 87 - sanity_check 376 ms # parallel group (20 tests): select_distinct_on select_having select_implicit delete random case prepared_xacts select_distinct select_into union portals namespace subselect arrays transactions btree_index aggregates update join hash_index ok 88 + select_into 462 ms ok 89 + select_distinct 461 ms ok 90 + select_distinct_on 106 ms ok 91 + select_implicit 137 ms ok 92 + select_having 123 ms ok 93 + subselect 1135 ms ok 94 + union 853 ms ok 95 + case 398 ms ok 96 + join 3840 ms ok 97 + aggregates 3319 ms ok 98 + transactions 2290 ms ok 99 + random 334 ms ok 100 + portals 980 ms ok 101 + arrays 1974 ms ok 102 + btree_index 3088 ms ok 103 + hash_index 6651 ms ok 104 + update 3331 ms ok 105 + delete 111 ms ok 106 + namespace 1053 ms ok 107 + prepared_xacts 387 ms # parallel group (20 tests): init_privs security_label drop_operator password collate lock tablesample object_address replica_identity matview groupingsets spgist gin gist identity generated rowsecurity join_hash brin privileges ok 108 + brin 5683 ms ok 109 + gin 2189 ms ok 110 + gist 2709 ms ok 111 + spgist 1894 ms ok 112 + privileges 6001 ms ok 113 + init_privs 188 ms ok 114 + security_label 237 ms ok 115 + collate 441 ms ok 116 + matview 1160 ms ok 117 + lock 575 ms ok 118 + replica_identity 906 ms ok 119 + rowsecurity 4119 ms ok 120 + object_address 599 ms ok 121 + tablesample 573 ms ok 122 + groupingsets 1150 ms ok 123 + drop_operator 292 ms ok 124 + password 359 ms ok 125 + identity 2783 ms ok 126 + generated 2820 ms ok 127 + join_hash 5517 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 207 ms ok 129 + brin_multi 2081 ms # parallel group (18 tests): tidscan collate.utf8 tidrangescan async alter_operator dbsize tid incremental_sort create_role alter_generic sysviews tsrf misc misc_functions create_table_like merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 2187 ms ok 131 + alter_generic 397 ms ok 132 + alter_operator 171 ms ok 133 + misc 598 ms ok 134 + async 152 ms ok 135 + dbsize 177 ms ok 136 + merge 3297 ms ok 137 + misc_functions 804 ms ok 138 + sysviews 455 ms ok 139 + tsrf 559 ms ok 140 + tid 189 ms ok 141 + tidscan 105 ms ok 142 + tidrangescan 102 ms ok 143 + collate.utf8 100 ms ok 144 + collate.icu.utf8 5767 ms ok 145 + incremental_sort 184 ms ok 146 + create_role 204 ms ok 147 + without_overlaps 5931 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 2235 ms ok 149 + psql 2131 ms ok 150 + psql_crosstab 134 ms ok 151 + amutils 91 ms ok 152 + stats_ext 3129 ms ok 153 + collate.linux.utf8 78 ms ok 154 + collate.windows.win1252 78 ms ok 155 - select_parallel 1404 ms ok 156 - write_parallel 225 ms ok 157 - vacuum_parallel 128 ms # parallel group (2 tests): subscription publication ok 158 + publication 2252 ms ok 159 + subscription 117 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap combocid dependency tsdicts guc functional_deps equivclass indirect_toast select_views window bitmapops tsearch cluster foreign_data foreign_key ok 160 + select_views 1751 ms ok 161 + portals_p2 238 ms ok 162 + foreign_key 6242 ms ok 163 + cluster 2574 ms ok 164 + dependency 487 ms ok 165 + guc 490 ms ok 166 + bitmapops 2086 ms ok 167 + combocid 428 ms ok 168 + tsearch 2113 ms ok 169 + tsdicts 466 ms ok 170 + foreign_data 2654 ms ok 171 + window 1937 ms ok 172 + xmlmap 313 ms ok 173 + functional_deps 437 ms ok 174 + advisory_lock 247 ms ok 175 + indirect_toast 987 ms ok 176 + equivclass 455 ms # parallel group (9 tests): sqljson_jsontable sqljson jsonpath jsonpath_encoding json_encoding sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 539 ms ok 178 + jsonb 882 ms ok 179 + json_encoding 340 ms ok 180 + jsonpath 259 ms ok 181 + jsonpath_encoding 316 ms ok 182 + jsonb_jsonpath 724 ms ok 183 + sqljson 144 ms ok 184 + sqljson_queryfuncs 386 ms ok 185 + sqljson_jsontable 107 ms # parallel group (18 tests): returning prepare conversion sequence polymorphism plancache with rowtypes limit temp largeobject copy2 rangefuncs xml truncate domain plpgsql alter_table ok 186 + plancache 1107 ms ok 187 + limit 1288 ms ok 188 + plpgsql 3628 ms ok 189 + copy2 1814 ms ok 190 + temp 1349 ms ok 191 + domain 3190 ms ok 192 + rangefuncs 1830 ms ok 193 + prepare 820 ms ok 194 + conversion 905 ms ok 195 + truncate 2300 ms ok 196 + alter_table 13780 ms ok 197 + sequence 897 ms ok 198 + polymorphism 999 ms ok 199 + rowtypes 1209 ms ok 200 + returning 78 ms ok 201 + largeobject 1287 ms ok 202 + with 1068 ms ok 203 + xml 1824 ms # parallel group (15 tests): predicate hash_part explain reloptions memoize partition_info compression partition_merge partition_aggregate partition_split tuplesort partition_prune stats partition_join indexing ok 204 + partition_merge 1139 ms ok 205 + partition_split 2335 ms not ok 206 + partition_join 6804 ms ok 207 + partition_prune 4484 ms ok 208 + reloptions 249 ms ok 209 + hash_part 211 ms ok 210 + indexing 6862 ms ok 211 + partition_aggregate 1988 ms ok 212 + partition_info 738 ms ok 213 + tuplesort 2569 ms ok 214 + explain 229 ms ok 215 + compression 881 ms ok 216 + memoize 702 ms ok 217 + stats 5925 ms ok 218 + predicate 39 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 431 ms ok 220 + event_trigger 1005 ms ok 221 - event_trigger_login 65 ms ok 222 - fast_default 1107 ms ok 223 - tablespace 1464 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-29 18:08:36 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out 2024-04-29 18:12:57 @@ -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 === [18:13:02.058](86.301s) not ok 5 - regression tests pass [18:13:02.059](0.001s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [18:13:02.059](0.000s) # got: '256' # expected: '0' # Checking port 63546 # Found port 63546 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=63546 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/DDVqyow89E Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [18:13:02.070](0.011s) # 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=63545 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/DDVqyow89E dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_5xgh/dump1.sql [18:13:08.300](6.230s) 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/DDVqyow89E -p 63545 -P 63546 --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 [18:13:09.251](0.951s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [18:13:09.251](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/DDVqyow89E -p 63545 -P 63546 --clone --check [18:13:11.331](2.081s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [18:13:11.338](0.006s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [18:13:11.338](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 21078 ### 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/DDVqyow89E -p 63545 -P 63546 --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* [18:13:17.189](5.851s) ok 12 - run of pg_upgrade --check for new instance [18:13:17.189](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/DDVqyow89E -p 63545 -P 63546 --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 [18:13:48.040](30.851s) ok 14 - run of pg_upgrade for new instance [18:13:48.040](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 23969 [18:13:48.599](0.559s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=63546 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/DDVqyow89E dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_5xgh/dump2.sql [18:14:00.376](11.777s) ok 17 - dump after running pg_upgrade [18:14:00.475](0.099s) ok 18 - old and new dumps match after pg_upgrade [18:14:00.475](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" [18:14:00.593](0.118s) # Looks like you failed 1 test of 18.