[05:38:29.980](0.026s) # testing using transfer mode --clone # Checking port 55333 # Found port 55333 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=55333 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/qliKToiAM_ Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [05:38:30.028](0.047s) # 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 9961 [05:38:32.313](2.285s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [05:38:32.494](0.181s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [05:38:32.666](0.172s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [05:38:32.756](0.090s) ok 4 - created database with ASCII characters from 91 to 127 [05:38:32.756](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/qliKToiAM_, port 55333 ok 1 - test_setup 275 ms # parallel group (20 tests): varchar char name pg_lsn txid text int2 oid int4 uuid money float4 regproc boolean int8 float8 bit enum numeric rangetypes ok 2 + boolean 191 ms ok 3 + char 142 ms ok 4 + name 147 ms ok 5 + varchar 130 ms ok 6 + text 159 ms ok 7 + int2 159 ms ok 8 + int4 166 ms ok 9 + int8 190 ms ok 10 + oid 157 ms ok 11 + float4 167 ms ok 12 + float8 184 ms ok 13 + bit 187 ms ok 14 + numeric 710 ms ok 15 + txid 126 ms ok 16 + uuid 140 ms ok 17 + enum 170 ms ok 18 + money 134 ms ok 19 + rangetypes 704 ms ok 20 + pg_lsn 94 ms ok 21 + regproc 126 ms # parallel group (20 tests): macaddr8 md5 lseg line path circle point time timetz inet macaddr interval numerology date polygon strings box multirangetypes timestamp timestamptz ok 22 + strings 257 ms ok 23 + md5 92 ms ok 24 + numerology 150 ms ok 25 + point 110 ms ok 26 + lseg 90 ms ok 27 + line 92 ms ok 28 + box 331 ms ok 29 + path 92 ms ok 30 + polygon 233 ms ok 31 + circle 86 ms ok 32 + date 146 ms ok 33 + time 90 ms ok 34 + timetz 93 ms ok 35 + timestamp 412 ms ok 36 + timestamptz 420 ms ok 37 + interval 106 ms ok 38 + inet 77 ms ok 39 + macaddr 99 ms ok 40 + macaddr8 36 ms ok 41 + multirangetypes 351 ms # parallel group (12 tests): misc_sanity comments mvcc unicode tstypes horology geometry xid expressions type_sanity opr_sanity regex ok 42 + geometry 225 ms ok 43 + horology 195 ms ok 44 + tstypes 173 ms ok 45 + regex 714 ms ok 46 + type_sanity 248 ms ok 47 + opr_sanity 491 ms ok 48 + misc_sanity 106 ms ok 49 + comments 110 ms ok 50 + expressions 209 ms ok 51 + unicode 125 ms ok 52 + xid 194 ms ok 53 + mvcc 117 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 251 ms ok 55 + copyselect 74 ms ok 56 + copydml 80 ms ok 57 + insert 518 ms ok 58 + insert_conflict 372 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 66 ms ok 60 + create_misc 106 ms ok 61 + create_operator 82 ms ok 62 + create_procedure 141 ms ok 63 + create_table 944 ms ok 64 + create_type 131 ms ok 65 + create_schema 65 ms # parallel group (5 tests): index_including_gist create_index_spgist index_including create_view create_index ok 66 + create_index 2318 ms ok 67 + create_index_spgist 626 ms ok 68 + create_view 1142 ms ok 69 + index_including 1082 ms ok 70 + index_including_gist 615 ms # parallel group (16 tests): roleattributes hash_func create_cast errors create_aggregate create_function_sql select drop_if_exists typed_table infinite_recurse create_am vacuum updatable_views constraints inherit triggers ok 71 + create_aggregate 168 ms ok 72 + create_function_sql 237 ms ok 73 + create_cast 162 ms ok 74 + constraints 1149 ms ok 75 + triggers 2345 ms ok 76 + select 277 ms ok 77 + inherit 1724 ms ok 78 + typed_table 474 ms ok 79 + vacuum 602 ms ok 80 + drop_if_exists 265 ms ok 81 + updatable_views 1109 ms ok 82 + roleattributes 127 ms ok 83 + create_am 505 ms ok 84 + hash_func 122 ms ok 85 + errors 120 ms ok 86 + infinite_recurse 434 ms ok 87 - sanity_check 136 ms # parallel group (20 tests): delete random namespace prepared_xacts select_distinct select_distinct_on select_having case select_implicit select_into portals transactions union arrays subselect update aggregates join hash_index btree_index ok 88 + select_into 271 ms ok 89 + select_distinct 228 ms ok 90 + select_distinct_on 234 ms ok 91 + select_implicit 264 ms ok 92 + select_having 240 ms ok 93 + subselect 1049 ms ok 94 + union 796 ms ok 95 + case 258 ms ok 96 + join 1505 ms ok 97 + aggregates 1271 ms ok 98 + transactions 455 ms ok 99 + random 129 ms ok 100 + portals 442 ms ok 101 + arrays 841 ms ok 102 + btree_index 2464 ms ok 103 + hash_index 2017 ms ok 104 + update 1255 ms ok 105 + delete 98 ms ok 106 + namespace 133 ms ok 107 + prepared_xacts 152 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock collate object_address replica_identity groupingsets generated matview spgist identity gin gist rowsecurity join_hash brin privileges ok 108 + brin 2139 ms ok 109 + gin 1189 ms ok 110 + gist 1217 ms ok 111 + spgist 1061 ms ok 112 + privileges 2353 ms ok 113 + init_privs 194 ms ok 114 + security_label 223 ms ok 115 + collate 605 ms ok 116 + matview 897 ms ok 117 + lock 490 ms ok 118 + replica_identity 648 ms ok 119 + rowsecurity 1231 ms ok 120 + object_address 592 ms ok 121 + tablesample 338 ms ok 122 + groupingsets 834 ms ok 123 + drop_operator 183 ms ok 124 + password 457 ms ok 125 + identity 1113 ms ok 126 + generated 843 ms ok 127 + join_hash 2074 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 54 ms ok 129 + brin_multi 641 ms # parallel group (18 tests): async dbsize tsrf alter_operator tidrangescan alter_generic tidscan collate.utf8 create_role misc_functions tid sysviews misc incremental_sort create_table_like collate.icu.utf8 without_overlaps merge ok 130 + create_table_like 468 ms ok 131 + alter_generic 220 ms ok 132 + alter_operator 178 ms ok 133 + misc 318 ms ok 134 + async 103 ms ok 135 + dbsize 134 ms ok 136 + merge 491 ms ok 137 + misc_functions 237 ms ok 138 + sysviews 285 ms ok 139 + tsrf 141 ms ok 140 + tid 243 ms ok 141 + tidscan 194 ms ok 142 + tidrangescan 150 ms ok 143 + collate.utf8 190 ms ok 144 + collate.icu.utf8 431 ms ok 145 + incremental_sort 284 ms ok 146 + create_role 199 ms ok 147 + without_overlaps 446 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 461 ms ok 149 + psql 344 ms ok 150 + psql_crosstab 41 ms ok 151 + amutils 35 ms ok 152 + stats_ext 983 ms ok 153 + collate.linux.utf8 28 ms ok 154 + collate.windows.win1252 27 ms ok 155 - select_parallel 754 ms ok 156 - write_parallel 117 ms ok 157 - vacuum_parallel 68 ms # parallel group (2 tests): subscription publication ok 158 + publication 569 ms not ok 159 + subscription 318 ms # parallel group (17 tests): advisory_lock xmlmap combocid functional_deps portals_p2 equivclass tsdicts guc dependency cluster select_views window indirect_toast bitmapops tsearch foreign_data foreign_key ok 160 + select_views 669 ms ok 161 + portals_p2 169 ms ok 162 + foreign_key 1197 ms ok 163 + cluster 516 ms ok 164 + dependency 200 ms ok 165 + guc 190 ms ok 166 + bitmapops 734 ms ok 167 + combocid 116 ms ok 168 + tsearch 819 ms ok 169 + tsdicts 172 ms ok 170 + foreign_data 916 ms ok 171 + window 656 ms ok 172 + xmlmap 88 ms ok 173 + functional_deps 102 ms ok 174 + advisory_lock 74 ms ok 175 + indirect_toast 687 ms ok 176 + equivclass 140 ms # parallel group (8 tests): jsonpath_encoding json_encoding sqljson jsonpath sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 448 ms ok 178 + jsonb 607 ms ok 179 + json_encoding 41 ms ok 180 + jsonpath 83 ms ok 181 + jsonpath_encoding 38 ms ok 182 + jsonb_jsonpath 458 ms ok 183 + sqljson 74 ms ok 184 + sqljson_queryfuncs 116 ms # parallel group (18 tests): prepare plancache temp truncate largeobject polymorphism sequence rangefuncs conversion limit returning with copy2 rowtypes domain xml plpgsql alter_table ok 185 + plancache 336 ms ok 186 + limit 646 ms ok 187 + plpgsql 2133 ms ok 188 + copy2 1009 ms ok 189 + temp 347 ms ok 190 + domain 1134 ms ok 191 + rangefuncs 529 ms ok 192 + prepare 144 ms ok 193 + conversion 574 ms ok 194 + truncate 364 ms ok 195 + alter_table 2583 ms ok 196 + sequence 444 ms ok 197 + polymorphism 385 ms ok 198 + rowtypes 1022 ms ok 199 + returning 593 ms ok 200 + largeobject 347 ms ok 201 + with 671 ms ok 202 + xml 2033 ms # parallel group (13 tests): hash_part predicate reloptions partition_info explain memoize compression partition_aggregate tuplesort stats partition_prune indexing partition_join ok 203 + partition_join 4347 ms ok 204 + partition_prune 2398 ms ok 205 + reloptions 268 ms ok 206 + hash_part 233 ms ok 207 + indexing 3622 ms ok 208 + partition_aggregate 1534 ms ok 209 + partition_info 461 ms ok 210 + tuplesort 2016 ms ok 211 + explain 455 ms ok 212 + compression 619 ms ok 213 + memoize 475 ms ok 214 + stats 2311 ms ok 215 + predicate 202 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 159 ms ok 217 + event_trigger 303 ms ok 218 - event_trigger_login 60 ms ok 219 - fast_default 195 ms ok 220 - tablespace 734 ms 1..220 # 1 of 220 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-04 05:36:19 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out 2024-04-04 05:38:51 @@ -381,14 +381,13 @@ --fail - alter of two_phase option not supported. ALTER SUBSCRIPTION regress_testsub SET (two_phase = false); -ERROR: unrecognized subscription parameter: "two_phase" -- but can alter streaming when two_phase enabled ALTER SUBSCRIPTION regress_testsub SET (streaming = true); \dRs+ List of subscriptions Name | Owner | Enabled | Publication | Binary | Streaming | Two-phase commit | Disable on error | Origin | Password required | Run as owner? | Failover | Synchronous commit | Conninfo | Skip LSN -----------------+---------------------------+---------+-------------+--------+-----------+------------------+------------------+--------+-------------------+---------------+----------+--------------------+-----------------------------+---------- - regress_testsub | regress_subscription_user | f | {testpub} | f | on | p | f | any | t | f | f | off | dbname=regress_doesnotexist | 0/0 + regress_testsub | regress_subscription_user | f | {testpub} | f | on | d | f | any | t | f | f | off | dbname=regress_doesnotexist | 0/0 (1 row) ALTER SUBSCRIPTION regress_testsub SET (slot_name = NONE); === EOF === [05:39:02.925](30.169s) not ok 5 - regression tests pass [05:39:02.926](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [05:39:02.926](0.000s) # got: '256' # expected: '0' # Checking port 55334 # Found port 55334 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=55334 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/qliKToiAM_ Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [05:39:02.938](0.012s) # 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=55333 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/qliKToiAM_ dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_8_9L/dump1.sql [05:39:06.312](3.374s) 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/qliKToiAM_ -p 55333 -P 55334 --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 [05:39:06.739](0.428s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [05:39:06.740](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/qliKToiAM_ -p 55333 -P 55334 --clone --check [05:39:08.090](1.350s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [05:39:08.090](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [05:39:08.090](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 18026 ### 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/qliKToiAM_ -p 55333 -P 55334 --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* [05:39:10.549](2.458s) ok 12 - run of pg_upgrade --check for new instance [05:39:10.549](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/qliKToiAM_ -p 55333 -P 55334 --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 [05:39:29.909](19.360s) ok 14 - run of pg_upgrade for new instance [05:39:29.909](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 21847 [05:39:30.460](0.551s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=55334 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/qliKToiAM_ dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_8_9L/dump2.sql [05:39:39.733](9.273s) ok 17 - dump after running pg_upgrade [05:39:40.758](1.024s) ok 18 - old and new dumps match after pg_upgrade [05:39:40.758](0.001s) 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" [05:39:40.872](0.114s) # Looks like you failed 1 test of 18.