[11:35:40.550](0.007s) # testing using transfer mode --clone # Checking port 51464 # Found port 51464 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=51464 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [11:35:40.612](0.062s) # 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 9583 [11:35:42.074](1.462s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [11:35:42.243](0.169s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [11:35:42.669](0.426s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [11:35:42.868](0.199s) ok 4 - created database with ASCII characters from 91 to 127 [11:35:42.868](0.000s) # running regression tests in old instance # using postmaster on /var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t, port 51464 ok 1 - test_setup 424 ms # parallel group (20 tests): int2 int4 text varchar char name int8 oid txid money regproc float4 boolean uuid bit pg_lsn enum float8 rangetypes numeric ok 2 + boolean 346 ms ok 3 + char 270 ms ok 4 + name 269 ms ok 5 + varchar 257 ms ok 6 + text 242 ms ok 7 + int2 204 ms ok 8 + int4 202 ms ok 9 + int8 246 ms ok 10 + oid 250 ms ok 11 + float4 265 ms ok 12 + float8 378 ms ok 13 + bit 309 ms ok 14 + numeric 992 ms ok 15 + txid 232 ms ok 16 + uuid 273 ms ok 17 + enum 322 ms ok 18 + money 213 ms ok 19 + rangetypes 826 ms ok 20 + pg_lsn 272 ms ok 21 + regproc 196 ms # parallel group (20 tests): md5 lseg path circle line point time macaddr timetz macaddr8 numerology date inet interval polygon strings timestamp timestamptz multirangetypes box ok 22 + strings 334 ms ok 23 + md5 89 ms ok 24 + numerology 149 ms ok 25 + point 121 ms ok 26 + lseg 89 ms ok 27 + line 113 ms ok 28 + box 518 ms ok 29 + path 102 ms ok 30 + polygon 232 ms ok 31 + circle 95 ms ok 32 + date 131 ms ok 33 + time 102 ms ok 34 + timetz 111 ms ok 35 + timestamp 425 ms ok 36 + timestamptz 451 ms ok 37 + interval 146 ms ok 38 + inet 121 ms ok 39 + macaddr 98 ms ok 40 + macaddr8 103 ms ok 41 + multirangetypes 466 ms # parallel group (12 tests): misc_sanity comments unicode mvcc geometry type_sanity xid expressions tstypes horology opr_sanity regex ok 42 + geometry 182 ms ok 43 + horology 297 ms ok 44 + tstypes 241 ms ok 45 + regex 565 ms ok 46 + type_sanity 209 ms ok 47 + opr_sanity 540 ms ok 48 + misc_sanity 54 ms ok 49 + comments 53 ms ok 50 + expressions 222 ms ok 51 + unicode 70 ms ok 52 + xid 206 ms ok 53 + mvcc 139 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 109 ms ok 55 + copyselect 67 ms ok 56 + copydml 66 ms ok 57 + insert 873 ms ok 58 + insert_conflict 462 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 138 ms ok 60 + create_misc 221 ms ok 61 + create_operator 162 ms ok 62 + create_procedure 226 ms ok 63 + create_table 671 ms ok 64 + create_type 201 ms ok 65 + create_schema 185 ms # parallel group (5 tests): index_including index_including_gist create_index_spgist create_view create_index ok 66 + create_index 4056 ms ok 67 + create_index_spgist 1045 ms ok 68 + create_view 1097 ms ok 69 + index_including 863 ms ok 70 + index_including_gist 880 ms # parallel group (16 tests): create_cast hash_func create_aggregate roleattributes select errors drop_if_exists typed_table create_function_sql create_am infinite_recurse vacuum constraints inherit updatable_views triggers ok 71 + create_aggregate 130 ms ok 72 + create_function_sql 290 ms ok 73 + create_cast 91 ms ok 74 + constraints 1473 ms ok 75 + triggers 2415 ms ok 76 + select 158 ms ok 77 + inherit 1814 ms ok 78 + typed_table 230 ms ok 79 + vacuum 1187 ms ok 80 + drop_if_exists 216 ms ok 81 + updatable_views 1810 ms ok 82 + roleattributes 129 ms ok 83 + create_am 349 ms ok 84 + hash_func 92 ms ok 85 + errors 130 ms ok 86 + infinite_recurse 478 ms ok 87 - sanity_check 79 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit select_into union select_distinct namespace prepared_xacts case transactions portals random arrays update subselect hash_index aggregates join btree_index ok 88 + select_into 399 ms ok 89 + select_distinct 418 ms ok 90 + select_distinct_on 145 ms ok 91 + select_implicit 375 ms ok 92 + select_having 225 ms ok 93 + subselect 1154 ms ok 94 + union 404 ms ok 95 + case 499 ms ok 96 + join 2401 ms ok 97 + aggregates 1875 ms ok 98 + transactions 550 ms ok 99 + random 618 ms ok 100 + portals 571 ms ok 101 + arrays 946 ms ok 102 + btree_index 2764 ms ok 103 + hash_index 1513 ms ok 104 + update 1036 ms ok 105 + delete 155 ms ok 106 + namespace 353 ms ok 107 + prepared_xacts 422 ms # parallel group (20 tests): init_privs security_label drop_operator object_address tablesample lock replica_identity password collate identity groupingsets matview generated spgist rowsecurity gin join_hash gist brin privileges ok 108 + brin 2612 ms ok 109 + gin 2476 ms ok 110 + gist 2604 ms ok 111 + spgist 2017 ms ok 112 + privileges 2834 ms ok 113 + init_privs 164 ms ok 114 + security_label 170 ms ok 115 + collate 931 ms ok 116 + matview 1355 ms ok 117 + lock 859 ms ok 118 + replica_identity 883 ms ok 119 + rowsecurity 2105 ms ok 120 + object_address 614 ms ok 121 + tablesample 621 ms ok 122 + groupingsets 1290 ms ok 123 + drop_operator 224 ms ok 124 + password 853 ms ok 125 + identity 948 ms ok 126 + generated 1623 ms ok 127 + join_hash 2447 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 86 ms ok 129 + brin_multi 823 ms # parallel group (18 tests): async dbsize tidrangescan collate.utf8 tidscan create_role sysviews alter_operator incremental_sort tsrf tid misc misc_functions alter_generic create_table_like merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 575 ms ok 131 + alter_generic 520 ms ok 132 + alter_operator 326 ms ok 133 + misc 487 ms ok 134 + async 183 ms ok 135 + dbsize 201 ms ok 136 + merge 833 ms ok 137 + misc_functions 480 ms ok 138 + sysviews 303 ms ok 139 + tsrf 313 ms ok 140 + tid 312 ms ok 141 + tidscan 241 ms ok 142 + tidrangescan 196 ms ok 143 + collate.utf8 213 ms ok 144 + collate.icu.utf8 912 ms ok 145 + incremental_sort 267 ms ok 146 + create_role 227 ms ok 147 + without_overlaps 1015 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 834 ms ok 149 + psql 961 ms ok 150 + psql_crosstab 84 ms ok 151 + amutils 61 ms ok 152 + stats_ext 1725 ms ok 153 + collate.linux.utf8 51 ms ok 154 + collate.windows.win1252 52 ms ok 155 - select_parallel 1710 ms ok 156 - write_parallel 224 ms ok 157 - vacuum_parallel 155 ms # parallel group (2 tests): subscription publication ok 158 + publication 1434 ms not ok 159 + subscription 222 ms # parallel group (17 tests): portals_p2 advisory_lock combocid xmlmap functional_deps indirect_toast dependency equivclass tsdicts select_views guc bitmapops cluster window tsearch foreign_data foreign_key ok 160 + select_views 434 ms ok 161 + portals_p2 148 ms ok 162 + foreign_key 7040 ms ok 163 + cluster 685 ms ok 164 + dependency 347 ms ok 165 + guc 433 ms ok 166 + bitmapops 440 ms ok 167 + combocid 229 ms ok 168 + tsearch 1315 ms ok 169 + tsdicts 336 ms ok 170 + foreign_data 1689 ms ok 171 + window 1125 ms ok 172 + xmlmap 281 ms ok 173 + functional_deps 306 ms ok 174 + advisory_lock 113 ms ok 175 + indirect_toast 305 ms ok 176 + equivclass 311 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath jsonb_jsonpath sqljson json sqljson_queryfuncs jsonb ok 177 + json 404 ms ok 178 + jsonb 1347 ms ok 179 + json_encoding 238 ms ok 180 + jsonpath 275 ms ok 181 + jsonpath_encoding 144 ms ok 182 + jsonb_jsonpath 370 ms ok 183 + sqljson 379 ms ok 184 + sqljson_queryfuncs 1316 ms ok 185 + sqljson_jsontable 235 ms # parallel group (18 tests): prepare limit plancache returning polymorphism largeobject rowtypes xml temp rangefuncs conversion with copy2 sequence truncate domain plpgsql alter_table ok 186 + plancache 412 ms ok 187 + limit 251 ms ok 188 + plpgsql 4605 ms ok 189 + copy2 3277 ms ok 190 + temp 2829 ms ok 191 + domain 3958 ms ok 192 + rangefuncs 2963 ms ok 193 + prepare 186 ms ok 194 + conversion 3097 ms ok 195 + truncate 3818 ms ok 196 + alter_table 10084 ms ok 197 + sequence 3360 ms ok 198 + polymorphism 1072 ms ok 199 + rowtypes 2231 ms ok 200 + returning 342 ms ok 201 + largeobject 1321 ms ok 202 + with 3070 ms ok 203 + xml 2323 ms # parallel group (15 tests): predicate hash_part explain partition_info reloptions memoize partition_aggregate compression tuplesort partition_merge partition_split stats partition_prune partition_join indexing ok 204 + partition_merge 3486 ms ok 205 + partition_split 5082 ms ok 206 + partition_join 8581 ms ok 207 + partition_prune 6375 ms ok 208 + reloptions 794 ms ok 209 + hash_part 416 ms ok 210 + indexing 8985 ms ok 211 + partition_aggregate 2241 ms ok 212 + partition_info 561 ms ok 213 + tuplesort 2646 ms ok 214 + explain 420 ms ok 215 + compression 2452 ms ok 216 + memoize 1151 ms ok 217 + stats 5073 ms ok 218 + predicate 316 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 129 ms ok 220 + event_trigger 806 ms ok 221 - event_trigger_login 267 ms ok 222 - fast_default 429 ms ok 223 - tablespace 3730 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/subscription.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out --- /Users/admin/pgsql/src/test/regress/expected/subscription.out 2024-04-07 11:34:16 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out 2024-04-07 11:36:10 @@ -381,7 +381,7 @@ --fail - alter of two_phase option not supported. ALTER SUBSCRIPTION regress_testsub SET (two_phase = false); -ERROR: unrecognized subscription parameter: "two_phase" +ERROR: could not connect to the publisher: connection to server on socket "/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t/.s.PGSQL.51464" failed: FATAL: number of requested standby connections exceeds max_wal_senders (currently 0) -- but can alter streaming when two_phase enabled ALTER SUBSCRIPTION regress_testsub SET (streaming = true); \dRs+ === EOF === [11:36:54.466](71.597s) not ok 5 - regression tests pass [11:36:54.466](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [11:36:54.466](0.000s) # got: '256' # expected: '0' # Checking port 51465 # Found port 51465 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=51465 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [11:36:54.474](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=51464 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_ZmTE/dump1.sql [11:37:03.092](8.618s) 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/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t -p 51464 -P 51465 --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 [11:37:04.792](1.700s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [11:37:04.792](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/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t -p 51464 -P 51465 --clone --check [11:37:08.331](3.539s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [11:37:08.331](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [11:37:08.331](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 21379 ### 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/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t -p 51464 -P 51465 --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* [11:37:13.832](5.501s) ok 12 - run of pg_upgrade --check for new instance [11:37:13.832](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/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t -p 51464 -P 51465 --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 [11:37:48.638](34.805s) ok 14 - run of pg_upgrade for new instance [11:37:48.638](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 24314 [11:37:48.779](0.142s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=51465 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/xHu4uD5c1t dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_ZmTE/dump2.sql [11:38:01.125](12.346s) ok 17 - dump after running pg_upgrade [11:38:01.244](0.119s) ok 18 - old and new dumps match after pg_upgrade [11:38:01.245](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" [11:38:01.384](0.140s) # Looks like you failed 1 test of 18.