[06:20:04.161](0.078s) # testing using transfer mode --clone # Checking port 65053 # Found port 65053 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=65053 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [06:20:04.178](0.017s) # 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 5656 [06:20:05.453](1.274s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [06:20:05.614](0.162s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [06:20:05.703](0.089s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [06:20:05.796](0.093s) ok 4 - created database with ASCII characters from 91 to 127 [06:20:05.796](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK, port 65053 ok 1 - test_setup 360 ms # parallel group (20 tests): varchar char pg_lsn name bit text money regproc int8 float8 enum txid int2 int4 oid float4 boolean uuid rangetypes numeric ok 2 + boolean 473 ms ok 3 + char 257 ms ok 4 + name 262 ms ok 5 + varchar 254 ms ok 6 + text 268 ms ok 7 + int2 397 ms ok 8 + int4 409 ms ok 9 + int8 274 ms ok 10 + oid 432 ms ok 11 + float4 438 ms ok 12 + float8 271 ms ok 13 + bit 249 ms ok 14 + numeric 811 ms ok 15 + txid 375 ms ok 16 + uuid 450 ms ok 17 + enum 257 ms ok 18 + money 236 ms ok 19 + rangetypes 731 ms ok 20 + pg_lsn 213 ms ok 21 + regproc 221 ms # parallel group (20 tests): md5 lseg path circle line numerology macaddr8 time macaddr timetz point inet interval polygon strings date box multirangetypes timestamp timestamptz ok 22 + strings 341 ms ok 23 + md5 96 ms ok 24 + numerology 235 ms ok 25 + point 261 ms ok 26 + lseg 107 ms ok 27 + line 176 ms ok 28 + box 468 ms ok 29 + path 123 ms ok 30 + polygon 326 ms ok 31 + circle 154 ms ok 32 + date 328 ms ok 33 + time 235 ms ok 34 + timetz 235 ms ok 35 + timestamp 472 ms ok 36 + timestamptz 565 ms ok 37 + interval 256 ms ok 38 + inet 230 ms ok 39 + macaddr 216 ms ok 40 + macaddr8 193 ms ok 41 + multirangetypes 448 ms # parallel group (12 tests): unicode comments misc_sanity xid expressions mvcc type_sanity tstypes geometry horology opr_sanity regex ok 42 + geometry 201 ms ok 43 + horology 215 ms ok 44 + tstypes 193 ms ok 45 + regex 572 ms ok 46 + type_sanity 187 ms ok 47 + opr_sanity 425 ms ok 48 + misc_sanity 62 ms ok 49 + comments 59 ms ok 50 + expressions 74 ms ok 51 + unicode 46 ms ok 52 + xid 66 ms ok 53 + mvcc 66 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 150 ms ok 55 + copyselect 90 ms ok 56 + copydml 82 ms ok 57 + insert 501 ms ok 58 + insert_conflict 237 ms # parallel group (7 tests): create_function_c create_misc create_schema create_operator create_type create_procedure create_table ok 59 + create_function_c 40 ms ok 60 + create_misc 153 ms ok 61 + create_operator 267 ms ok 62 + create_procedure 322 ms ok 63 + create_table 806 ms ok 64 + create_type 316 ms ok 65 + create_schema 259 ms # parallel group (5 tests): index_including index_including_gist create_index_spgist create_view create_index ok 66 + create_index 1494 ms ok 67 + create_index_spgist 552 ms ok 68 + create_view 691 ms ok 69 + index_including 389 ms ok 70 + index_including_gist 391 ms # parallel group (16 tests): hash_func roleattributes errors drop_if_exists create_cast create_aggregate create_am typed_table select create_function_sql infinite_recurse constraints vacuum updatable_views inherit triggers ok 71 + create_aggregate 125 ms ok 72 + create_function_sql 425 ms ok 73 + create_cast 114 ms ok 74 + constraints 1138 ms ok 75 + triggers 3149 ms ok 76 + select 289 ms ok 77 + inherit 2358 ms ok 78 + typed_table 276 ms ok 79 + vacuum 1326 ms ok 80 + drop_if_exists 76 ms ok 81 + updatable_views 2051 ms ok 82 + roleattributes 61 ms ok 83 + create_am 176 ms ok 84 + hash_func 51 ms ok 85 + errors 51 ms ok 86 + infinite_recurse 553 ms ok 87 - sanity_check 94 ms # parallel group (20 tests): delete select_distinct_on case select_having select_implicit namespace random select_into portals prepared_xacts select_distinct union transactions subselect arrays update aggregates hash_index join btree_index ok 88 + select_into 311 ms ok 89 + select_distinct 393 ms ok 90 + select_distinct_on 172 ms ok 91 + select_implicit 259 ms ok 92 + select_having 183 ms ok 93 + subselect 988 ms ok 94 + union 540 ms ok 95 + case 164 ms ok 96 + join 1906 ms ok 97 + aggregates 1514 ms ok 98 + transactions 538 ms ok 99 + random 283 ms ok 100 + portals 321 ms ok 101 + arrays 1016 ms ok 102 + btree_index 2196 ms ok 103 + hash_index 1704 ms ok 104 + update 1340 ms ok 105 + delete 132 ms ok 106 + namespace 247 ms ok 107 + prepared_xacts 330 ms # parallel group (20 tests): security_label init_privs drop_operator password tablesample replica_identity lock collate object_address groupingsets spgist gin identity gist matview generated rowsecurity join_hash brin privileges ok 108 + brin 2605 ms ok 109 + gin 1132 ms ok 110 + gist 1188 ms ok 111 + spgist 1021 ms ok 112 + privileges 2780 ms ok 113 + init_privs 149 ms ok 114 + security_label 132 ms ok 115 + collate 387 ms ok 116 + matview 1225 ms ok 117 + lock 369 ms ok 118 + replica_identity 348 ms ok 119 + rowsecurity 1359 ms ok 120 + object_address 391 ms ok 121 + tablesample 335 ms ok 122 + groupingsets 970 ms ok 123 + drop_operator 127 ms ok 124 + password 271 ms ok 125 + identity 1132 ms ok 126 + generated 1228 ms ok 127 + join_hash 2538 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 59 ms ok 129 + brin_multi 524 ms # parallel group (18 tests): async dbsize collate.utf8 tidrangescan tid tidscan alter_operator tsrf misc sysviews create_role alter_generic misc_functions incremental_sort create_table_like collate.icu.utf8 without_overlaps merge ok 130 + create_table_like 589 ms ok 131 + alter_generic 266 ms ok 132 + alter_operator 160 ms ok 133 + misc 180 ms ok 134 + async 107 ms ok 135 + dbsize 121 ms ok 136 + merge 725 ms ok 137 + misc_functions 340 ms ok 138 + sysviews 198 ms ok 139 + tsrf 159 ms ok 140 + tid 135 ms ok 141 + tidscan 132 ms ok 142 + tidrangescan 127 ms ok 143 + collate.utf8 106 ms ok 144 + collate.icu.utf8 631 ms ok 145 + incremental_sort 322 ms ok 146 + create_role 184 ms ok 147 + without_overlaps 676 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 762 ms ok 149 + psql 749 ms ok 150 + psql_crosstab 89 ms ok 151 + amutils 61 ms ok 152 + stats_ext 1557 ms ok 153 + collate.linux.utf8 45 ms ok 154 + collate.windows.win1252 46 ms ok 155 - select_parallel 749 ms ok 156 - write_parallel 97 ms ok 157 - vacuum_parallel 624 ms # parallel group (2 tests): subscription publication ok 158 + publication 310 ms not ok 159 + subscription 124 ms # parallel group (17 tests): portals_p2 advisory_lock guc combocid equivclass tsdicts xmlmap functional_deps select_views dependency window bitmapops tsearch indirect_toast cluster foreign_data foreign_key ok 160 + select_views 322 ms ok 161 + portals_p2 218 ms ok 162 + foreign_key 1438 ms ok 163 + cluster 640 ms ok 164 + dependency 373 ms ok 165 + guc 269 ms ok 166 + bitmapops 470 ms ok 167 + combocid 270 ms ok 168 + tsearch 478 ms ok 169 + tsdicts 284 ms ok 170 + foreign_data 809 ms ok 171 + window 415 ms ok 172 + xmlmap 282 ms ok 173 + functional_deps 282 ms ok 174 + advisory_lock 202 ms ok 175 + indirect_toast 585 ms ok 176 + equivclass 240 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs jsonb_jsonpath json jsonb ok 177 + json 315 ms ok 178 + jsonb 749 ms ok 179 + json_encoding 68 ms ok 180 + jsonpath 239 ms ok 181 + jsonpath_encoding 63 ms ok 182 + jsonb_jsonpath 287 ms ok 183 + sqljson 242 ms ok 184 + sqljson_queryfuncs 282 ms ok 185 + sqljson_jsontable 217 ms # parallel group (18 tests): prepare returning limit plancache conversion temp polymorphism rangefuncs with rowtypes sequence copy2 largeobject domain truncate xml plpgsql alter_table ok 186 + plancache 378 ms ok 187 + limit 186 ms ok 188 + plpgsql 1755 ms ok 189 + copy2 636 ms ok 190 + temp 402 ms ok 191 + domain 689 ms ok 192 + rangefuncs 487 ms ok 193 + prepare 92 ms ok 194 + conversion 370 ms ok 195 + truncate 706 ms ok 196 + alter_table 3278 ms ok 197 + sequence 619 ms ok 198 + polymorphism 432 ms ok 199 + rowtypes 572 ms ok 200 + returning 159 ms ok 201 + largeobject 618 ms ok 202 + with 553 ms ok 203 + xml 1341 ms # parallel group (15 tests): predicate hash_part explain partition_info memoize reloptions partition_merge compression partition_split stats partition_prune partition_aggregate indexing tuplesort partition_join ok 204 + partition_merge 459 ms ok 205 + partition_split 690 ms ok 206 + partition_join 1904 ms ok 207 + partition_prune 1331 ms ok 208 + reloptions 304 ms ok 209 + hash_part 185 ms ok 210 + indexing 1684 ms ok 211 + partition_aggregate 1534 ms ok 212 + partition_info 263 ms ok 213 + tuplesort 1858 ms ok 214 + explain 210 ms ok 215 + compression 439 ms ok 216 + memoize 277 ms ok 217 + stats 1268 ms ok 218 + predicate 137 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 638 ms ok 220 + event_trigger 706 ms ok 221 - event_trigger_login 39 ms ok 222 - fast_default 164 ms ok 223 - tablespace 1247 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-11 06:18:26 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out 2024-04-11 06:20:26 @@ -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/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK/.s.PGSQL.65053" 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 === [06:20:38.103](32.307s) not ok 5 - regression tests pass [06:20:38.104](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [06:20:38.104](0.000s) # got: '256' # expected: '0' # Checking port 65054 # Found port 65054 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=65054 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [06:20:38.123](0.019s) # 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=65053 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jqUL/dump1.sql [06:20:43.265](5.143s) 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/OLcG3KvdUK -p 65053 -P 65054 --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 [06:20:43.715](0.449s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [06:20:43.715](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/OLcG3KvdUK -p 65053 -P 65054 --clone --check [06:20:44.913](1.199s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [06:20:44.914](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [06:20:44.914](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 14425 ### 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/OLcG3KvdUK -p 65053 -P 65054 --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* [06:20:47.650](2.736s) ok 12 - run of pg_upgrade --check for new instance [06:20:47.650](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/OLcG3KvdUK -p 65053 -P 65054 --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 [06:21:06.554](18.904s) ok 14 - run of pg_upgrade for new instance [06:21:06.554](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 18117 [06:21:06.704](0.149s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=65054 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/OLcG3KvdUK dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jqUL/dump2.sql [06:21:13.023](6.319s) ok 17 - dump after running pg_upgrade [06:21:13.629](0.607s) ok 18 - old and new dumps match after pg_upgrade [06:21:13.629](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" [06:21:13.746](0.116s) # Looks like you failed 1 test of 18.