[11:35:43.428](0.013s) # testing using transfer mode --clone # Checking port 61868 # Found port 61868 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=61868 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/IhRWCWNhrU Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [11:35:43.530](0.102s) # 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 9658 [11:35:45.715](2.185s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [11:35:46.499](0.784s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [11:35:46.832](0.333s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [11:35:47.174](0.342s) ok 4 - created database with ASCII characters from 91 to 127 [11:35:47.175](0.000s) # running regression tests in old instance # using postmaster on /var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/IhRWCWNhrU, port 61868 ok 1 - test_setup 538 ms # parallel group (20 tests): varchar char name oid pg_lsn txid uuid text int2 int4 boolean money float4 regproc int8 bit float8 enum numeric rangetypes ok 2 + boolean 124 ms ok 3 + char 93 ms ok 4 + name 94 ms ok 5 + varchar 84 ms ok 6 + text 107 ms ok 7 + int2 107 ms ok 8 + int4 111 ms ok 9 + int8 121 ms ok 10 + oid 83 ms ok 11 + float4 109 ms ok 12 + float8 143 ms ok 13 + bit 138 ms ok 14 + numeric 512 ms ok 15 + txid 81 ms ok 16 + uuid 83 ms ok 17 + enum 132 ms ok 18 + money 91 ms ok 19 + rangetypes 500 ms ok 20 + pg_lsn 62 ms ok 21 + regproc 81 ms # parallel group (20 tests): lseg path line circle time timetz macaddr macaddr8 inet date polygon interval md5 point numerology strings box timestamp multirangetypes timestamptz ok 22 + strings 231 ms ok 23 + md5 151 ms ok 24 + numerology 166 ms ok 25 + point 161 ms ok 26 + lseg 44 ms ok 27 + line 61 ms ok 28 + box 353 ms ok 29 + path 55 ms ok 30 + polygon 122 ms ok 31 + circle 44 ms ok 32 + date 91 ms ok 33 + time 55 ms ok 34 + timetz 57 ms ok 35 + timestamp 400 ms ok 36 + timestamptz 549 ms ok 37 + interval 102 ms ok 38 + inet 83 ms ok 39 + macaddr 63 ms ok 40 + macaddr8 67 ms ok 41 + multirangetypes 412 ms # parallel group (12 tests): unicode expressions xid comments geometry misc_sanity tstypes horology opr_sanity type_sanity mvcc regex ok 42 + geometry 207 ms ok 43 + horology 251 ms ok 44 + tstypes 226 ms ok 45 + regex 725 ms ok 46 + type_sanity 307 ms ok 47 + opr_sanity 262 ms ok 48 + misc_sanity 208 ms ok 49 + comments 188 ms ok 50 + expressions 161 ms ok 51 + unicode 144 ms ok 52 + xid 162 ms ok 53 + mvcc 292 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 103 ms ok 55 + copyselect 56 ms ok 56 + copydml 60 ms ok 57 + insert 653 ms ok 58 + insert_conflict 342 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 29 ms ok 60 + create_misc 154 ms ok 61 + create_operator 40 ms ok 62 + create_procedure 153 ms ok 63 + create_table 581 ms ok 64 + create_type 103 ms ok 65 + create_schema 42 ms # parallel group (5 tests): create_index_spgist index_including_gist index_including create_view create_index ok 66 + create_index 3490 ms ok 67 + create_index_spgist 563 ms ok 68 + create_view 1676 ms ok 69 + index_including 1629 ms ok 70 + index_including_gist 737 ms # parallel group (16 tests): create_cast hash_func create_aggregate errors roleattributes select typed_table drop_if_exists create_am create_function_sql infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 122 ms ok 72 + create_function_sql 405 ms ok 73 + create_cast 90 ms ok 74 + constraints 1414 ms ok 75 + triggers 2490 ms ok 76 + select 168 ms ok 77 + inherit 1750 ms ok 78 + typed_table 189 ms ok 79 + vacuum 1252 ms ok 80 + drop_if_exists 187 ms ok 81 + updatable_views 1519 ms ok 82 + roleattributes 111 ms ok 83 + create_am 198 ms ok 84 + hash_func 84 ms ok 85 + errors 95 ms ok 86 + infinite_recurse 394 ms ok 87 - sanity_check 150 ms # parallel group (20 tests): select_having select_distinct_on select_implicit prepared_xacts case union select_into delete namespace random select_distinct arrays portals subselect transactions update aggregates btree_index join hash_index ok 88 + select_into 199 ms ok 89 + select_distinct 331 ms ok 90 + select_distinct_on 124 ms ok 91 + select_implicit 123 ms ok 92 + select_having 122 ms ok 93 + subselect 853 ms ok 94 + union 190 ms ok 95 + case 188 ms ok 96 + join 3188 ms ok 97 + aggregates 1438 ms ok 98 + transactions 877 ms ok 99 + random 233 ms ok 100 + portals 776 ms ok 101 + arrays 750 ms ok 102 + btree_index 2243 ms ok 103 + hash_index 3286 ms ok 104 + update 1233 ms ok 105 + delete 160 ms ok 106 + namespace 170 ms ok 107 + prepared_xacts 144 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample lock collate password object_address groupingsets replica_identity spgist gin identity gist generated matview rowsecurity brin join_hash privileges ok 108 + brin 4596 ms ok 109 + gin 1860 ms ok 110 + gist 2223 ms ok 111 + spgist 1488 ms ok 112 + privileges 5264 ms ok 113 + init_privs 507 ms ok 114 + security_label 581 ms ok 115 + collate 875 ms ok 116 + matview 3235 ms ok 117 + lock 842 ms ok 118 + replica_identity 1302 ms ok 119 + rowsecurity 3491 ms ok 120 + object_address 898 ms ok 121 + tablesample 818 ms ok 122 + groupingsets 1250 ms ok 123 + drop_operator 485 ms ok 124 + password 829 ms ok 125 + identity 1916 ms ok 126 + generated 2739 ms ok 127 + join_hash 4507 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 310 ms ok 129 + brin_multi 972 ms # parallel group (18 tests): async dbsize collate.utf8 tidrangescan tidscan create_role sysviews tid alter_generic tsrf alter_operator misc incremental_sort misc_functions create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 343 ms ok 131 + alter_generic 195 ms ok 132 + alter_operator 223 ms ok 133 + misc 244 ms ok 134 + async 83 ms ok 135 + dbsize 114 ms ok 136 + merge 600 ms ok 137 + misc_functions 265 ms ok 138 + sysviews 147 ms ok 139 + tsrf 196 ms ok 140 + tid 169 ms ok 141 + tidscan 118 ms ok 142 + tidrangescan 109 ms ok 143 + collate.utf8 94 ms ok 144 + collate.icu.utf8 576 ms ok 145 + incremental_sort 225 ms ok 146 + create_role 117 ms ok 147 + without_overlaps 875 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 603 ms ok 149 + psql 632 ms ok 150 + psql_crosstab 84 ms ok 151 + amutils 55 ms ok 152 + stats_ext 1477 ms ok 153 + collate.linux.utf8 43 ms ok 154 + collate.windows.win1252 49 ms ok 155 - select_parallel 1022 ms ok 156 - write_parallel 435 ms ok 157 - vacuum_parallel 171 ms # parallel group (2 tests): subscription publication ok 158 + publication 947 ms not ok 159 + subscription 216 ms # parallel group (17 tests): portals_p2 combocid dependency functional_deps advisory_lock equivclass tsdicts xmlmap guc indirect_toast select_views window bitmapops tsearch foreign_data cluster foreign_key ok 160 + select_views 973 ms ok 161 + portals_p2 174 ms ok 162 + foreign_key 8130 ms ok 163 + cluster 2014 ms ok 164 + dependency 292 ms ok 165 + guc 464 ms ok 166 + bitmapops 1452 ms ok 167 + combocid 235 ms ok 168 + tsearch 1505 ms ok 169 + tsdicts 353 ms ok 170 + foreign_data 1814 ms ok 171 + window 1339 ms ok 172 + xmlmap 356 ms ok 173 + functional_deps 296 ms ok 174 + advisory_lock 299 ms ok 175 + indirect_toast 856 ms ok 176 + equivclass 296 ms # parallel group (9 tests): json_encoding jsonpath_encoding sqljson_jsontable jsonpath sqljson json jsonb_jsonpath jsonb sqljson_queryfuncs ok 177 + json 474 ms ok 178 + jsonb 1162 ms ok 179 + json_encoding 94 ms ok 180 + jsonpath 172 ms ok 181 + jsonpath_encoding 135 ms ok 182 + jsonb_jsonpath 757 ms ok 183 + sqljson 402 ms ok 184 + sqljson_queryfuncs 1547 ms ok 185 + sqljson_jsontable 123 ms # parallel group (18 tests): prepare limit returning polymorphism plancache conversion temp rowtypes domain largeobject copy2 truncate with sequence rangefuncs xml plpgsql alter_table ok 186 + plancache 865 ms ok 187 + limit 537 ms ok 188 + plpgsql 2795 ms ok 189 + copy2 1384 ms ok 190 + temp 1081 ms ok 191 + domain 1288 ms ok 192 + rangefuncs 1564 ms ok 193 + prepare 355 ms ok 194 + conversion 956 ms ok 195 + truncate 1379 ms ok 196 + alter_table 7321 ms ok 197 + sequence 1382 ms ok 198 + polymorphism 558 ms ok 199 + rowtypes 1083 ms ok 200 + returning 484 ms ok 201 + largeobject 1311 ms ok 202 + with 1336 ms ok 203 + xml 1924 ms # parallel group (13 tests): partition_info explain hash_part predicate memoize reloptions compression partition_aggregate tuplesort partition_prune stats partition_join indexing ok 204 + partition_join 6938 ms ok 205 + partition_prune 4977 ms ok 206 + reloptions 487 ms ok 207 + hash_part 125 ms ok 208 + indexing 7029 ms ok 209 + partition_aggregate 896 ms ok 210 + partition_info 72 ms ok 211 + tuplesort 1756 ms ok 212 + explain 97 ms ok 213 + compression 617 ms ok 214 + memoize 235 ms ok 215 + stats 5952 ms ok 216 + predicate 147 ms # parallel group (2 tests): oidjoins event_trigger ok 217 + oidjoins 218 ms ok 218 + event_trigger 753 ms ok 219 - event_trigger_login 30 ms ok 220 - fast_default 581 ms ok 221 - tablespace 3622 ms 1..221 # 1 of 221 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-05 11:34:23 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out 2024-04-05 11:36:14 @@ -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/IhRWCWNhrU/.s.PGSQL.61868" 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:51.924](64.749s) not ok 5 - regression tests pass [11:36:51.924](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [11:36:51.924](0.000s) # got: '256' # expected: '0' # Checking port 61869 # Found port 61869 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=61869 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/IhRWCWNhrU Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [11:36:51.962](0.038s) # 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=61868 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/IhRWCWNhrU dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jl31/dump1.sql [11:37:00.478](8.515s) 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/IhRWCWNhrU -p 61868 -P 61869 --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:02.842](2.364s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [11:37:02.842](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/IhRWCWNhrU -p 61868 -P 61869 --clone --check [11:37:06.510](3.668s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [11:37:06.510](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [11:37:06.510](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 21226 ### 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/IhRWCWNhrU -p 61868 -P 61869 --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:11.241](4.731s) ok 12 - run of pg_upgrade --check for new instance [11:37:11.569](0.328s) 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/IhRWCWNhrU -p 61868 -P 61869 --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.131](36.562s) ok 14 - run of pg_upgrade for new instance [11:37:48.131](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 24121 [11:37:48.812](0.681s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=61869 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/IhRWCWNhrU dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_jl31/dump2.sql [11:38:04.624](15.812s) ok 17 - dump after running pg_upgrade [11:38:05.288](0.664s) ok 18 - old and new dumps match after pg_upgrade [11:38:05.288](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:05.521](0.232s) # Looks like you failed 1 test of 18.