[07:37:50.582](0.134s) # testing using transfer mode --clone # Checking port 59519 # Found port 59519 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=59519 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/Xk5bRdiJsr Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [07:37:50.592](0.010s) # 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 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: default collation provider: builtin default collation locale: C 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 7461 [07:37:52.452](1.860s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [07:37:52.620](0.168s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [07:37:52.801](0.181s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [07:37:52.970](0.169s) ok 4 - created database with ASCII characters from 91 to 127 [07:37:52.970](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/Xk5bRdiJsr, port 59519 ok 1 - test_setup 280 ms # parallel group (20 tests): float4 varchar float8 txid bit pg_lsn uuid money regproc char oid name int2 boolean int4 text int8 enum rangetypes numeric ok 2 + boolean 233 ms ok 3 + char 218 ms ok 4 + name 220 ms ok 5 + varchar 96 ms ok 6 + text 232 ms ok 7 + int2 226 ms ok 8 + int4 226 ms ok 9 + int8 230 ms ok 10 + oid 208 ms ok 11 + float4 81 ms ok 12 + float8 90 ms ok 13 + bit 89 ms ok 14 + numeric 843 ms ok 15 + txid 80 ms ok 16 + uuid 140 ms ok 17 + enum 223 ms ok 18 + money 171 ms ok 19 + rangetypes 511 ms ok 20 + pg_lsn 116 ms ok 21 + regproc 170 ms # parallel group (20 tests): md5 lseg path circle line point time macaddr timetz macaddr8 numerology inet date interval strings polygon box timestamp multirangetypes timestamptz ok 22 + strings 242 ms ok 23 + md5 135 ms ok 24 + numerology 181 ms ok 25 + point 159 ms ok 26 + lseg 140 ms ok 27 + line 152 ms ok 28 + box 361 ms ok 29 + path 138 ms ok 30 + polygon 285 ms ok 31 + circle 128 ms ok 32 + date 169 ms ok 33 + time 133 ms ok 34 + timetz 138 ms ok 35 + timestamp 517 ms ok 36 + timestamptz 594 ms ok 37 + interval 162 ms ok 38 + inet 126 ms ok 39 + macaddr 103 ms ok 40 + macaddr8 110 ms ok 41 + multirangetypes 544 ms # parallel group (12 tests): misc_sanity comments unicode mvcc geometry xid tstypes expressions type_sanity horology opr_sanity regex ok 42 + geometry 160 ms ok 43 + horology 243 ms ok 44 + tstypes 170 ms ok 45 + regex 909 ms ok 46 + type_sanity 198 ms ok 47 + opr_sanity 740 ms ok 48 + misc_sanity 86 ms ok 49 + comments 85 ms ok 50 + expressions 159 ms ok 51 + unicode 109 ms ok 52 + xid 143 ms ok 53 + mvcc 113 ms # parallel group (5 tests): copyselect copydml insert_conflict copy insert ok 54 + copy 315 ms ok 55 + copyselect 62 ms ok 56 + copydml 75 ms ok 57 + insert 480 ms ok 58 + insert_conflict 309 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_procedure create_misc create_table ok 59 + create_function_c 34 ms ok 60 + create_misc 86 ms ok 61 + create_operator 50 ms ok 62 + create_procedure 63 ms ok 63 + create_table 727 ms ok 64 + create_type 55 ms ok 65 + create_schema 46 ms # parallel group (5 tests): index_including_gist create_index_spgist index_including create_view create_index ok 66 + create_index 2464 ms ok 67 + create_index_spgist 837 ms ok 68 + create_view 1295 ms ok 69 + index_including 934 ms ok 70 + index_including_gist 639 ms # parallel group (16 tests): create_cast hash_func create_aggregate roleattributes errors select drop_if_exists typed_table infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 199 ms ok 72 + create_function_sql 501 ms ok 73 + create_cast 150 ms ok 74 + constraints 1615 ms ok 75 + triggers 3445 ms ok 76 + select 200 ms ok 77 + inherit 2525 ms ok 78 + typed_table 299 ms ok 79 + vacuum 1003 ms ok 80 + drop_if_exists 252 ms ok 81 + updatable_views 2444 ms ok 82 + roleattributes 175 ms ok 83 + create_am 504 ms ok 84 + hash_func 131 ms ok 85 + errors 162 ms ok 86 + infinite_recurse 370 ms ok 87 - sanity_check 75 ms # parallel group (20 tests): select_distinct_on select_having select_distinct case select_implicit transactions union delete namespace portals random select_into prepared_xacts arrays subselect update aggregates hash_index join btree_index ok 88 + select_into 557 ms ok 89 + select_distinct 204 ms ok 90 + select_distinct_on 146 ms ok 91 + select_implicit 214 ms ok 92 + select_having 171 ms ok 93 + subselect 965 ms ok 94 + union 241 ms ok 95 + case 181 ms ok 96 + join 1688 ms ok 97 + aggregates 1519 ms ok 98 + transactions 200 ms ok 99 + random 386 ms ok 100 + portals 351 ms ok 101 + arrays 805 ms ok 102 + btree_index 2003 ms ok 103 + hash_index 1652 ms ok 104 + update 927 ms ok 105 + delete 266 ms ok 106 + namespace 284 ms ok 107 + prepared_xacts 477 ms # parallel group (20 tests): init_privs drop_operator security_label object_address lock tablesample password collate replica_identity groupingsets identity matview rowsecurity spgist generated gin gist join_hash brin privileges ok 108 + brin 1830 ms ok 109 + gin 1357 ms ok 110 + gist 1467 ms ok 111 + spgist 1069 ms ok 112 + privileges 2234 ms ok 113 + init_privs 102 ms ok 114 + security_label 149 ms ok 115 + collate 536 ms ok 116 + matview 1006 ms ok 117 + lock 239 ms ok 118 + replica_identity 560 ms ok 119 + rowsecurity 1016 ms ok 120 + object_address 186 ms ok 121 + tablesample 257 ms ok 122 + groupingsets 567 ms ok 123 + drop_operator 90 ms ok 124 + password 272 ms ok 125 + identity 823 ms ok 126 + generated 1112 ms ok 127 + join_hash 1755 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 54 ms ok 129 + brin_multi 542 ms # parallel group (17 tests): async dbsize tidrangescan incremental_sort alter_operator tidscan tid misc tsrf create_role misc_functions sysviews alter_generic without_overlaps create_table_like merge collate.icu.utf8 ok 130 + create_table_like 532 ms ok 131 + alter_generic 240 ms ok 132 + alter_operator 138 ms ok 133 + misc 149 ms ok 134 + async 84 ms ok 135 + dbsize 86 ms ok 136 + merge 573 ms ok 137 + misc_functions 206 ms not ok 138 + sysviews 206 ms ok 139 + tsrf 138 ms ok 140 + tid 127 ms ok 141 + tidscan 121 ms ok 142 + tidrangescan 111 ms ok 143 + collate.icu.utf8 560 ms ok 144 + incremental_sort 106 ms ok 145 + create_role 139 ms ok 146 + without_overlaps 402 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 147 + rules 682 ms ok 148 + psql 475 ms ok 149 + psql_crosstab 65 ms ok 150 + amutils 48 ms ok 151 + stats_ext 1229 ms ok 152 + collate.linux.utf8 41 ms ok 153 + collate.windows.win1252 41 ms ok 154 - select_parallel 1162 ms ok 155 - write_parallel 82 ms ok 156 - vacuum_parallel 62 ms # parallel group (2 tests): subscription publication ok 157 + publication 281 ms ok 158 + subscription 106 ms # parallel group (17 tests): advisory_lock xmlmap functional_deps equivclass window portals_p2 tsdicts guc combocid dependency select_views tsearch indirect_toast bitmapops cluster foreign_data foreign_key ok 159 + select_views 500 ms ok 160 + portals_p2 216 ms ok 161 + foreign_key 1643 ms ok 162 + cluster 714 ms ok 163 + dependency 482 ms ok 164 + guc 408 ms ok 165 + bitmapops 621 ms ok 166 + combocid 426 ms ok 167 + tsearch 526 ms ok 168 + tsdicts 339 ms ok 169 + foreign_data 789 ms ok 170 + window 144 ms ok 171 + xmlmap 71 ms ok 172 + functional_deps 66 ms ok 173 + advisory_lock 59 ms ok 174 + indirect_toast 508 ms ok 175 + equivclass 64 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson jsonb_jsonpath json jsonb ok 176 + json 262 ms ok 177 + jsonb 486 ms ok 178 + json_encoding 88 ms ok 179 + jsonpath 131 ms ok 180 + jsonpath_encoding 77 ms ok 181 + jsonb_jsonpath 224 ms ok 182 + sqljson 122 ms # parallel group (18 tests): prepare returning temp with largeobject polymorphism limit rowtypes sequence conversion plancache copy2 truncate domain rangefuncs plpgsql xml alter_table ok 183 + plancache 645 ms ok 184 + limit 478 ms ok 185 + plpgsql 1883 ms ok 186 + copy2 655 ms ok 187 + temp 339 ms ok 188 + domain 784 ms ok 189 + rangefuncs 786 ms ok 190 + prepare 184 ms ok 191 + conversion 613 ms ok 192 + truncate 667 ms ok 193 + alter_table 2573 ms ok 194 + sequence 567 ms ok 195 + polymorphism 370 ms ok 196 + rowtypes 531 ms ok 197 + returning 215 ms ok 198 + largeobject 301 ms ok 199 + with 287 ms ok 200 + xml 1936 ms # parallel group (13 tests): predicate memoize reloptions explain hash_part partition_info compression partition_aggregate tuplesort stats partition_prune partition_join indexing ok 201 + partition_join 2668 ms ok 202 + partition_prune 2101 ms ok 203 + reloptions 205 ms ok 204 + hash_part 332 ms ok 205 + indexing 3107 ms ok 206 + partition_aggregate 1104 ms ok 207 + partition_info 357 ms ok 208 + tuplesort 1815 ms ok 209 + explain 222 ms ok 210 + compression 429 ms ok 211 + memoize 129 ms ok 212 + stats 1822 ms ok 213 + predicate 74 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 282 ms ok 215 + event_trigger 373 ms ok 216 - event_trigger_login 39 ms ok 217 - fast_default 389 ms ok 218 - tablespace 1413 ms 1..218 # 1 of 218 tests failed. # The differences that caused some tests to fail can be viewed in the file "/Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs". # A copy of the test summary that you see above is saved in the file "/Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /Users/admin/pgsql/src/test/regress/expected/sysviews.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /Users/admin/pgsql/src/test/regress/expected/sysviews.out 2024-03-17 07:34:22 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-17 07:38:09 @@ -134,7 +134,8 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) + enable_toast_cache | off +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [07:38:24.177](31.206s) not ok 5 - regression tests pass [07:38:24.177](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [07:38:24.177](0.000s) # got: '256' # expected: '0' # Checking port 59520 # Found port 59520 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=59520 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/Xk5bRdiJsr Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [07:38:24.184](0.006s) # 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: default collation 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=59519 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/Xk5bRdiJsr dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_76yi/dump1.sql [07:38:29.821](5.637s) 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/Xk5bRdiJsr -p 59519 -P 59520 --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 [07:38:30.614](0.792s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [07:38:30.614](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/Xk5bRdiJsr -p 59519 -P 59520 --clone --check [07:38:32.946](2.332s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [07:38:32.946](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [07:38:32.946](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 16359 ### 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/Xk5bRdiJsr -p 59519 -P 59520 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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* [07:38:34.924](1.978s) ok 12 - run of pg_upgrade --check for new instance [07:38:34.925](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/Xk5bRdiJsr -p 59519 -P 59520 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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 [07:38:54.786](19.861s) ok 14 - run of pg_upgrade for new instance [07:38:54.786](0.001s) 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 20153 [07:38:55.093](0.307s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=59520 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/Xk5bRdiJsr dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_76yi/dump2.sql [07:39:04.871](9.778s) ok 17 - dump after running pg_upgrade [07:39:05.060](0.189s) ok 18 - old and new dumps match after pg_upgrade [07:39:05.061](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" [07:39:05.173](0.112s) # Looks like you failed 1 test of 18.