[02:40:03.909](0.080s) # testing using transfer mode --clone # Checking port 56723 # Found port 56723 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=56723 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/LxUifTvkea Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [02:40:03.938](0.029s) # 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 9736 [02:40:05.493](1.555s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [02:40:05.865](0.372s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [02:40:05.975](0.110s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [02:40:06.110](0.134s) ok 4 - created database with ASCII characters from 91 to 127 [02:40:06.110](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/LxUifTvkea, port 56723 ok 1 - test_setup 375 ms # parallel group (20 tests): varchar char name oid pg_lsn txid float4 int4 regproc int8 text uuid int2 money float8 boolean enum bit numeric rangetypes ok 2 + boolean 262 ms ok 3 + char 101 ms ok 4 + name 108 ms ok 5 + varchar 93 ms ok 6 + text 182 ms ok 7 + int2 216 ms ok 8 + int4 154 ms ok 9 + int8 163 ms ok 10 + oid 96 ms ok 11 + float4 139 ms ok 12 + float8 233 ms ok 13 + bit 245 ms ok 14 + numeric 478 ms ok 15 + txid 120 ms ok 16 + uuid 157 ms ok 17 + enum 231 ms ok 18 + money 207 ms ok 19 + rangetypes 525 ms ok 20 + pg_lsn 69 ms ok 21 + regproc 114 ms # parallel group (20 tests): circle time timetz macaddr macaddr8 inet date interval md5 numerology point lseg line path polygon strings multirangetypes box timestamp timestamptz ok 22 + strings 298 ms ok 23 + md5 128 ms ok 24 + numerology 149 ms ok 25 + point 161 ms ok 26 + lseg 160 ms ok 27 + line 164 ms ok 28 + box 437 ms ok 29 + path 159 ms ok 30 + polygon 266 ms ok 31 + circle 52 ms ok 32 + date 78 ms ok 33 + time 50 ms ok 34 + timetz 53 ms ok 35 + timestamp 490 ms ok 36 + timestamptz 515 ms ok 37 + interval 68 ms ok 38 + inet 48 ms ok 39 + macaddr 34 ms ok 40 + macaddr8 41 ms ok 41 + multirangetypes 317 ms # parallel group (12 tests): comments misc_sanity unicode type_sanity expressions xid tstypes geometry mvcc horology opr_sanity regex ok 42 + geometry 101 ms ok 43 + horology 114 ms ok 44 + tstypes 97 ms ok 45 + regex 354 ms ok 46 + type_sanity 77 ms ok 47 + opr_sanity 319 ms ok 48 + misc_sanity 41 ms ok 49 + comments 40 ms ok 50 + expressions 73 ms ok 51 + unicode 42 ms ok 52 + xid 69 ms ok 53 + mvcc 82 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 206 ms ok 55 + copyselect 81 ms ok 56 + copydml 78 ms ok 57 + insert 772 ms ok 58 + insert_conflict 375 ms # parallel group (7 tests): create_function_c create_schema create_operator create_type create_misc create_procedure create_table ok 59 + create_function_c 61 ms ok 60 + create_misc 180 ms ok 61 + create_operator 155 ms ok 62 + create_procedure 180 ms ok 63 + create_table 806 ms ok 64 + create_type 163 ms ok 65 + create_schema 142 ms # parallel group (5 tests): create_index_spgist index_including index_including_gist create_view create_index ok 66 + create_index 2022 ms ok 67 + create_index_spgist 459 ms ok 68 + create_view 788 ms ok 69 + index_including 704 ms ok 70 + index_including_gist 721 ms # parallel group (16 tests): hash_func create_cast roleattributes errors create_aggregate drop_if_exists select infinite_recurse typed_table create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 234 ms ok 72 + create_function_sql 323 ms ok 73 + create_cast 224 ms ok 74 + constraints 2182 ms ok 75 + triggers 3075 ms ok 76 + select 280 ms ok 77 + inherit 2751 ms ok 78 + typed_table 316 ms ok 79 + vacuum 1695 ms ok 80 + drop_if_exists 251 ms ok 81 + updatable_views 2731 ms ok 82 + roleattributes 211 ms ok 83 + create_am 894 ms ok 84 + hash_func 188 ms ok 85 + errors 207 ms ok 86 + infinite_recurse 263 ms ok 87 - sanity_check 485 ms # parallel group (20 tests): select_distinct_on select_having delete select_implicit case namespace random select_distinct prepared_xacts select_into transactions portals union subselect arrays update hash_index aggregates btree_index join ok 88 + select_into 274 ms ok 89 + select_distinct 197 ms ok 90 + select_distinct_on 91 ms ok 91 + select_implicit 145 ms ok 92 + select_having 124 ms ok 93 + subselect 501 ms ok 94 + union 488 ms ok 95 + case 164 ms ok 96 + join 2351 ms ok 97 + aggregates 1385 ms ok 98 + transactions 322 ms ok 99 + random 157 ms ok 100 + portals 456 ms ok 101 + arrays 582 ms ok 102 + btree_index 2270 ms ok 103 + hash_index 1331 ms ok 104 + update 1119 ms ok 105 + delete 94 ms ok 106 + namespace 131 ms ok 107 + prepared_xacts 150 ms # parallel group (20 tests): drop_operator tablesample object_address password lock init_privs replica_identity collate security_label groupingsets matview generated identity spgist rowsecurity gist gin join_hash brin privileges ok 108 + brin 2455 ms ok 109 + gin 2022 ms ok 110 + gist 1688 ms ok 111 + spgist 1653 ms ok 112 + privileges 2696 ms ok 113 + init_privs 393 ms ok 114 + security_label 534 ms ok 115 + collate 394 ms ok 116 + matview 995 ms ok 117 + lock 260 ms ok 118 + replica_identity 373 ms ok 119 + rowsecurity 1629 ms ok 120 + object_address 156 ms ok 121 + tablesample 150 ms ok 122 + groupingsets 881 ms ok 123 + drop_operator 137 ms ok 124 + password 77 ms ok 125 + identity 1185 ms ok 126 + generated 1031 ms ok 127 + join_hash 2247 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 104 ms ok 129 + brin_multi 525 ms # parallel group (18 tests): async dbsize collate.utf8 tid tidrangescan tidscan alter_operator misc tsrf create_role incremental_sort sysviews alter_generic misc_functions collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 680 ms ok 131 + alter_generic 549 ms ok 132 + alter_operator 158 ms ok 133 + misc 164 ms ok 134 + async 92 ms ok 135 + dbsize 109 ms ok 136 + merge 730 ms ok 137 + misc_functions 553 ms ok 138 + sysviews 469 ms ok 139 + tsrf 178 ms ok 140 + tid 126 ms ok 141 + tidscan 131 ms ok 142 + tidrangescan 120 ms ok 143 + collate.utf8 97 ms ok 144 + collate.icu.utf8 635 ms ok 145 + incremental_sort 311 ms ok 146 + create_role 285 ms ok 147 + without_overlaps 979 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1428 ms ok 149 + psql 1111 ms ok 150 + psql_crosstab 102 ms ok 151 + amutils 79 ms ok 152 + stats_ext 2019 ms ok 153 + collate.linux.utf8 64 ms ok 154 + collate.windows.win1252 64 ms ok 155 - select_parallel 668 ms ok 156 - write_parallel 104 ms ok 157 - vacuum_parallel 89 ms # parallel group (2 tests): subscription publication ok 158 + publication 948 ms ok 159 + subscription 141 ms # parallel group (17 tests): portals_p2 advisory_lock combocid functional_deps xmlmap tsdicts equivclass guc dependency select_views window bitmapops indirect_toast cluster foreign_data tsearch foreign_key ok 160 + select_views 328 ms ok 161 + portals_p2 136 ms ok 162 + foreign_key 2033 ms ok 163 + cluster 1102 ms ok 164 + dependency 250 ms ok 165 + guc 235 ms ok 166 + bitmapops 449 ms ok 167 + combocid 186 ms ok 168 + tsearch 1357 ms ok 169 + tsdicts 209 ms ok 170 + foreign_data 1248 ms ok 171 + window 419 ms ok 172 + xmlmap 190 ms ok 173 + functional_deps 174 ms ok 174 + advisory_lock 103 ms ok 175 + indirect_toast 431 ms ok 176 + equivclass 184 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson json jsonb_jsonpath sqljson_queryfuncs jsonb ok 177 + json 212 ms ok 178 + jsonb 371 ms ok 179 + json_encoding 65 ms ok 180 + jsonpath 172 ms ok 181 + jsonpath_encoding 59 ms ok 182 + jsonb_jsonpath 234 ms ok 183 + sqljson 176 ms ok 184 + sqljson_queryfuncs 251 ms ok 185 + sqljson_jsontable 126 ms # parallel group (18 tests): prepare with copy2 polymorphism returning limit plancache largeobject conversion rangefuncs temp domain truncate rowtypes sequence xml plpgsql alter_table ok 186 + plancache 382 ms ok 187 + limit 371 ms ok 188 + plpgsql 2188 ms ok 189 + copy2 282 ms ok 190 + temp 713 ms ok 191 + domain 889 ms ok 192 + rangefuncs 709 ms ok 193 + prepare 100 ms ok 194 + conversion 674 ms ok 195 + truncate 887 ms ok 196 + alter_table 4548 ms ok 197 + sequence 1030 ms ok 198 + polymorphism 262 ms ok 199 + rowtypes 907 ms ok 200 + returning 258 ms ok 201 + largeobject 494 ms ok 202 + with 183 ms ok 203 + xml 1178 ms # parallel group (15 tests): predicate explain memoize partition_info hash_part reloptions compression partition_merge partition_split partition_aggregate stats tuplesort partition_prune indexing partition_join ok 204 + partition_merge 503 ms ok 205 + partition_split 1339 ms not ok 206 + partition_join 2798 ms ok 207 + partition_prune 2122 ms ok 208 + reloptions 304 ms ok 209 + hash_part 243 ms ok 210 + indexing 2269 ms ok 211 + partition_aggregate 1928 ms ok 212 + partition_info 157 ms ok 213 + tuplesort 1984 ms ok 214 + explain 131 ms ok 215 + compression 439 ms ok 216 + memoize 137 ms ok 217 + stats 1939 ms ok 218 + predicate 106 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 312 ms ok 220 + event_trigger 600 ms ok 221 - event_trigger_login 85 ms ok 222 - fast_default 480 ms ok 223 - tablespace 1951 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-24 02:37:33 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out 2024-04-24 02:40:38 @@ -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 === [02:40:43.305](37.195s) not ok 5 - regression tests pass [02:40:43.305](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [02:40:43.305](0.000s) # got: '256' # expected: '0' # Checking port 56724 # Found port 56724 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=56724 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/LxUifTvkea Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [02:40:43.310](0.005s) # 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=56723 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/LxUifTvkea dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_1vo6/dump1.sql [02:40:49.883](6.573s) 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/LxUifTvkea -p 56723 -P 56724 --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 [02:40:50.826](0.943s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [02:40:50.826](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/LxUifTvkea -p 56723 -P 56724 --clone --check [02:40:52.937](2.111s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [02:40:52.937](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [02:40:52.937](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 18965 ### 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/LxUifTvkea -p 56723 -P 56724 --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* [02:40:55.730](2.794s) ok 12 - run of pg_upgrade --check for new instance [02:40:55.731](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/LxUifTvkea -p 56723 -P 56724 --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 [02:41:11.713](15.982s) ok 14 - run of pg_upgrade for new instance [02:41:11.713](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 22170 [02:41:11.872](0.159s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=56724 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/LxUifTvkea dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_1vo6/dump2.sql [02:41:18.124](6.252s) ok 17 - dump after running pg_upgrade [02:41:18.422](0.298s) ok 18 - old and new dumps match after pg_upgrade [02:41:18.422](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" [02:41:18.604](0.182s) # Looks like you failed 1 test of 18.