[12:30:36.352](0.013s) # testing using transfer mode --clone # Checking port 60364 # Found port 60364 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=60364 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/YUFAqoo6vi Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [12:30:36.394](0.042s) # 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 5472 [12:30:38.275](1.882s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [12:30:38.348](0.073s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [12:30:38.454](0.106s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [12:30:38.615](0.161s) ok 4 - created database with ASCII characters from 91 to 127 [12:30:38.616](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/YUFAqoo6vi, port 60364 ok 1 - test_setup 435 ms # parallel group (20 tests): varchar char name oid pg_lsn float8 bit int2 txid int4 uuid text boolean float4 regproc int8 enum money rangetypes numeric ok 2 + boolean 211 ms ok 3 + char 122 ms ok 4 + name 143 ms ok 5 + varchar 110 ms ok 6 + text 201 ms ok 7 + int2 181 ms ok 8 + int4 186 ms ok 9 + int8 213 ms ok 10 + oid 144 ms ok 11 + float4 186 ms ok 12 + float8 148 ms ok 13 + bit 149 ms ok 14 + numeric 906 ms ok 15 + txid 151 ms ok 16 + uuid 156 ms ok 17 + enum 193 ms ok 18 + money 245 ms ok 19 + rangetypes 538 ms ok 20 + pg_lsn 109 ms ok 21 + regproc 151 ms # parallel group (20 tests): md5 lseg path circle line point time macaddr timetz numerology macaddr8 inet date interval strings polygon timestamp box multirangetypes timestamptz ok 22 + strings 287 ms ok 23 + md5 80 ms ok 24 + numerology 130 ms ok 25 + point 114 ms ok 26 + lseg 83 ms ok 27 + line 102 ms ok 28 + box 487 ms ok 29 + path 91 ms ok 30 + polygon 303 ms ok 31 + circle 88 ms ok 32 + date 225 ms ok 33 + time 98 ms ok 34 + timetz 100 ms ok 35 + timestamp 452 ms ok 36 + timestamptz 624 ms ok 37 + interval 245 ms ok 38 + inet 151 ms ok 39 + macaddr 85 ms ok 40 + macaddr8 93 ms ok 41 + multirangetypes 599 ms # parallel group (12 tests): misc_sanity comments unicode type_sanity expressions xid geometry tstypes horology opr_sanity mvcc regex ok 42 + geometry 208 ms ok 43 + horology 236 ms ok 44 + tstypes 208 ms ok 45 + regex 528 ms ok 46 + type_sanity 174 ms ok 47 + opr_sanity 237 ms ok 48 + misc_sanity 75 ms ok 49 + comments 71 ms ok 50 + expressions 165 ms ok 51 + unicode 94 ms ok 52 + xid 160 ms ok 53 + mvcc 217 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 100 ms ok 55 + copyselect 54 ms ok 56 + copydml 62 ms ok 57 + insert 725 ms ok 58 + insert_conflict 396 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 49 ms ok 60 + create_misc 136 ms ok 61 + create_operator 100 ms ok 62 + create_procedure 134 ms ok 63 + create_table 557 ms ok 64 + create_type 115 ms ok 65 + create_schema 112 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2698 ms ok 67 + create_index_spgist 803 ms ok 68 + create_view 972 ms ok 69 + index_including 784 ms ok 70 + index_including_gist 736 ms # parallel group (16 tests): create_cast hash_func errors create_aggregate roleattributes drop_if_exists select typed_table create_am create_function_sql vacuum infinite_recurse constraints updatable_views inherit triggers ok 71 + create_aggregate 112 ms ok 72 + create_function_sql 276 ms ok 73 + create_cast 98 ms ok 74 + constraints 818 ms ok 75 + triggers 2778 ms ok 76 + select 193 ms ok 77 + inherit 1103 ms ok 78 + typed_table 239 ms ok 79 + vacuum 477 ms ok 80 + drop_if_exists 153 ms ok 81 + updatable_views 1038 ms ok 82 + roleattributes 106 ms ok 83 + create_am 252 ms ok 84 + hash_func 94 ms ok 85 + errors 97 ms ok 86 + infinite_recurse 488 ms ok 87 - sanity_check 171 ms # parallel group (20 tests): select_distinct_on select_having delete case select_implicit select_into random prepared_xacts namespace union select_distinct portals subselect update arrays transactions hash_index aggregates btree_index join ok 88 + select_into 177 ms ok 89 + select_distinct 435 ms ok 90 + select_distinct_on 80 ms ok 91 + select_implicit 163 ms ok 92 + select_having 109 ms ok 93 + subselect 591 ms ok 94 + union 416 ms ok 95 + case 123 ms ok 96 + join 2383 ms ok 97 + aggregates 1630 ms ok 98 + transactions 1514 ms ok 99 + random 357 ms ok 100 + portals 421 ms ok 101 + arrays 1376 ms ok 102 + btree_index 1794 ms ok 103 + hash_index 1574 ms ok 104 + update 581 ms ok 105 + delete 87 ms ok 106 + namespace 351 ms ok 107 + prepared_xacts 347 ms # parallel group (20 tests): init_privs drop_operator security_label lock tablesample password object_address collate replica_identity matview groupingsets identity spgist rowsecurity gin gist generated brin join_hash privileges ok 108 + brin 2191 ms ok 109 + gin 1609 ms ok 110 + gist 1638 ms ok 111 + spgist 1375 ms ok 112 + privileges 2599 ms ok 113 + init_privs 94 ms ok 114 + security_label 340 ms ok 115 + collate 646 ms ok 116 + matview 923 ms ok 117 + lock 345 ms ok 118 + replica_identity 832 ms ok 119 + rowsecurity 1549 ms ok 120 + object_address 400 ms ok 121 + tablesample 339 ms ok 122 + groupingsets 920 ms ok 123 + drop_operator 314 ms ok 124 + password 356 ms ok 125 + identity 1065 ms ok 126 + generated 1603 ms ok 127 + join_hash 2160 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 49 ms ok 129 + brin_multi 779 ms # parallel group (18 tests): async dbsize collate.utf8 tid sysviews tidrangescan tidscan alter_operator misc tsrf create_role incremental_sort misc_functions alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 707 ms ok 131 + alter_generic 395 ms ok 132 + alter_operator 172 ms ok 133 + misc 173 ms ok 134 + async 92 ms ok 135 + dbsize 119 ms ok 136 + merge 801 ms ok 137 + misc_functions 378 ms ok 138 + sysviews 149 ms ok 139 + tsrf 166 ms ok 140 + tid 141 ms ok 141 + tidscan 148 ms ok 142 + tidrangescan 140 ms ok 143 + collate.utf8 108 ms ok 144 + collate.icu.utf8 534 ms ok 145 + incremental_sort 337 ms ok 146 + create_role 208 ms ok 147 + without_overlaps 860 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 607 ms ok 149 + psql 793 ms ok 150 + psql_crosstab 49 ms ok 151 + amutils 39 ms ok 152 + stats_ext 1611 ms ok 153 + collate.linux.utf8 33 ms ok 154 + collate.windows.win1252 31 ms ok 155 - select_parallel 1079 ms ok 156 - write_parallel 152 ms ok 157 - vacuum_parallel 66 ms # parallel group (2 tests): subscription publication ok 158 + publication 566 ms ok 159 + subscription 98 ms # parallel group (17 tests): portals_p2 functional_deps equivclass dependency advisory_lock combocid xmlmap tsdicts guc select_views tsearch cluster window indirect_toast bitmapops foreign_data foreign_key ok 160 + select_views 368 ms ok 161 + portals_p2 90 ms ok 162 + foreign_key 2099 ms ok 163 + cluster 508 ms ok 164 + dependency 113 ms ok 165 + guc 227 ms ok 166 + bitmapops 720 ms ok 167 + combocid 156 ms ok 168 + tsearch 406 ms ok 169 + tsdicts 183 ms ok 170 + foreign_data 772 ms ok 171 + window 492 ms ok 172 + xmlmap 149 ms ok 173 + functional_deps 68 ms ok 174 + advisory_lock 93 ms ok 175 + indirect_toast 667 ms ok 176 + equivclass 69 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_queryfuncs sqljson_jsontable sqljson jsonpath jsonb_jsonpath json jsonb ok 177 + json 534 ms ok 178 + jsonb 700 ms ok 179 + json_encoding 69 ms ok 180 + jsonpath 454 ms ok 181 + jsonpath_encoding 64 ms ok 182 + jsonb_jsonpath 516 ms ok 183 + sqljson 443 ms ok 184 + sqljson_queryfuncs 101 ms ok 185 + sqljson_jsontable 106 ms # parallel group (18 tests): prepare returning temp limit conversion sequence plancache domain polymorphism truncate rowtypes copy2 with rangefuncs largeobject xml plpgsql alter_table ok 186 + plancache 402 ms ok 187 + limit 287 ms ok 188 + plpgsql 1610 ms ok 189 + copy2 641 ms ok 190 + temp 280 ms ok 191 + domain 488 ms ok 192 + rangefuncs 641 ms ok 193 + prepare 86 ms ok 194 + conversion 344 ms ok 195 + truncate 557 ms ok 196 + alter_table 4013 ms ok 197 + sequence 340 ms ok 198 + polymorphism 534 ms ok 199 + rowtypes 580 ms ok 200 + returning 197 ms ok 201 + largeobject 673 ms ok 202 + with 610 ms ok 203 + xml 1396 ms # parallel group (15 tests): predicate partition_info explain memoize compression hash_part reloptions partition_merge partition_split partition_aggregate tuplesort stats partition_prune partition_join indexing ok 204 + partition_merge 827 ms ok 205 + partition_split 944 ms not ok 206 + partition_join 2158 ms ok 207 + partition_prune 2135 ms ok 208 + reloptions 162 ms ok 209 + hash_part 147 ms ok 210 + indexing 2389 ms ok 211 + partition_aggregate 1187 ms ok 212 + partition_info 79 ms ok 213 + tuplesort 1373 ms ok 214 + explain 76 ms ok 215 + compression 113 ms ok 216 + memoize 80 ms ok 217 + stats 1610 ms ok 218 + predicate 47 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 339 ms ok 220 + event_trigger 587 ms ok 221 - event_trigger_login 81 ms ok 222 - fast_default 969 ms ok 223 - tablespace 1177 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-05-05 12:28:48 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out 2024-05-05 12:31:10 @@ -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 === [12:31:13.653](35.038s) not ok 5 - regression tests pass [12:31:13.654](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [12:31:13.654](0.000s) # got: '256' # expected: '0' # Checking port 60365 # Found port 60365 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=60365 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/YUFAqoo6vi Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [12:31:13.662](0.008s) # 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=60364 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/YUFAqoo6vi dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_3G1h/dump1.sql [12:31:19.659](5.997s) 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/YUFAqoo6vi -p 60364 -P 60365 --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 [12:31:20.435](0.776s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [12:31:20.435](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/YUFAqoo6vi -p 60364 -P 60365 --clone --check [12:31:22.182](1.747s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [12:31:22.182](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [12:31:22.182](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 14681 ### 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/YUFAqoo6vi -p 60364 -P 60365 --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* [12:31:24.406](2.224s) ok 12 - run of pg_upgrade --check for new instance [12:31:24.407](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/YUFAqoo6vi -p 60364 -P 60365 --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 [12:31:39.937](15.531s) ok 14 - run of pg_upgrade for new instance [12:31:39.938](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 18096 [12:31:40.241](0.303s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=60365 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/YUFAqoo6vi dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_3G1h/dump2.sql [12:31:45.625](5.385s) ok 17 - dump after running pg_upgrade [12:31:45.948](0.322s) ok 18 - old and new dumps match after pg_upgrade [12:31:45.948](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" [12:31:46.058](0.110s) # Looks like you failed 1 test of 18.