[15:41:47.745](0.017s) # testing using transfer mode --clone # Checking port 64275 # Found port 64275 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=64275 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/Z2ShTUMOhG Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [15:41:47.769](0.024s) # 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 5333 [15:41:49.911](2.142s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [15:41:50.113](0.202s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [15:41:50.274](0.160s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [15:41:50.522](0.248s) ok 4 - created database with ASCII characters from 91 to 127 [15:41:50.522](0.000s) # running regression tests in old instance # using postmaster on /var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/Z2ShTUMOhG, port 64275 ok 1 - test_setup 605 ms # parallel group (20 tests): pg_lsn float4 int8 int2 int4 text oid char varchar name regproc txid boolean money uuid float8 bit enum numeric rangetypes ok 2 + boolean 289 ms ok 3 + char 183 ms ok 4 + name 185 ms ok 5 + varchar 181 ms ok 6 + text 143 ms ok 7 + int2 135 ms ok 8 + int4 139 ms ok 9 + int8 112 ms ok 10 + oid 166 ms ok 11 + float4 101 ms ok 12 + float8 432 ms ok 13 + bit 439 ms ok 14 + numeric 961 ms ok 15 + txid 232 ms ok 16 + uuid 271 ms ok 17 + enum 432 ms ok 18 + money 253 ms ok 19 + rangetypes 955 ms ok 20 + pg_lsn 51 ms ok 21 + regproc 140 ms # parallel group (20 tests): md5 circle line lseg point inet path time timetz numerology macaddr macaddr8 interval date multirangetypes strings polygon box timestamp timestamptz ok 22 + strings 235 ms ok 23 + md5 88 ms ok 24 + numerology 153 ms ok 25 + point 127 ms ok 26 + lseg 113 ms ok 27 + line 92 ms ok 28 + box 354 ms ok 29 + path 117 ms ok 30 + polygon 309 ms ok 31 + circle 71 ms ok 32 + date 150 ms ok 33 + time 108 ms ok 34 + timetz 115 ms ok 35 + timestamp 440 ms ok 36 + timestamptz 492 ms ok 37 + interval 132 ms ok 38 + inet 84 ms ok 39 + macaddr 104 ms ok 40 + macaddr8 106 ms ok 41 + multirangetypes 139 ms # parallel group (12 tests): misc_sanity comments unicode tstypes mvcc horology xid geometry expressions type_sanity opr_sanity regex ok 42 + geometry 209 ms ok 43 + horology 181 ms ok 44 + tstypes 171 ms ok 45 + regex 431 ms ok 46 + type_sanity 237 ms ok 47 + opr_sanity 372 ms ok 48 + misc_sanity 69 ms ok 49 + comments 75 ms ok 50 + expressions 217 ms ok 51 + unicode 86 ms ok 52 + xid 164 ms ok 53 + mvcc 150 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 162 ms ok 55 + copyselect 54 ms ok 56 + copydml 60 ms ok 57 + insert 1317 ms ok 58 + insert_conflict 397 ms # parallel group (7 tests): create_function_c create_operator create_misc create_schema create_type create_procedure create_table ok 59 + create_function_c 60 ms ok 60 + create_misc 170 ms ok 61 + create_operator 67 ms ok 62 + create_procedure 216 ms ok 63 + create_table 1743 ms ok 64 + create_type 172 ms ok 65 + create_schema 155 ms # parallel group (5 tests): index_including_gist create_index_spgist index_including create_view create_index ok 66 + create_index 2507 ms ok 67 + create_index_spgist 498 ms ok 68 + create_view 841 ms ok 69 + index_including 539 ms ok 70 + index_including_gist 465 ms # parallel group (16 tests): hash_func roleattributes select errors typed_table create_cast create_aggregate create_function_sql create_am drop_if_exists infinite_recurse vacuum constraints inherit updatable_views triggers ok 71 + create_aggregate 164 ms ok 72 + create_function_sql 185 ms ok 73 + create_cast 155 ms ok 74 + constraints 1317 ms ok 75 + triggers 4219 ms ok 76 + select 105 ms ok 77 + inherit 2703 ms ok 78 + typed_table 135 ms ok 79 + vacuum 1230 ms ok 80 + drop_if_exists 177 ms ok 81 + updatable_views 2802 ms ok 82 + roleattributes 78 ms ok 83 + create_am 160 ms ok 84 + hash_func 64 ms ok 85 + errors 74 ms ok 86 + infinite_recurse 415 ms ok 87 - sanity_check 504 ms # parallel group (20 tests): select_distinct_on select_having case select_implicit delete namespace prepared_xacts random select_into union transactions subselect select_distinct portals arrays update aggregates hash_index btree_index join ok 88 + select_into 330 ms ok 89 + select_distinct 462 ms ok 90 + select_distinct_on 92 ms ok 91 + select_implicit 175 ms ok 92 + select_having 133 ms ok 93 + subselect 447 ms ok 94 + union 391 ms ok 95 + case 163 ms ok 96 + join 2266 ms ok 97 + aggregates 1712 ms ok 98 + transactions 426 ms ok 99 + random 287 ms ok 100 + portals 553 ms ok 101 + arrays 695 ms ok 102 + btree_index 1870 ms ok 103 + hash_index 1753 ms ok 104 + update 1011 ms ok 105 + delete 223 ms ok 106 + namespace 233 ms ok 107 + prepared_xacts 231 ms # parallel group (20 tests): lock security_label init_privs password drop_operator tablesample object_address collate replica_identity groupingsets spgist gin gist matview identity generated rowsecurity brin join_hash privileges ok 108 + brin 4704 ms ok 109 + gin 1960 ms ok 110 + gist 2427 ms ok 111 + spgist 1687 ms ok 112 + privileges 4866 ms ok 113 + init_privs 552 ms ok 114 + security_label 527 ms ok 115 + collate 828 ms ok 116 + matview 2871 ms ok 117 + lock 402 ms ok 118 + replica_identity 820 ms ok 119 + rowsecurity 3926 ms ok 120 + object_address 765 ms ok 121 + tablesample 660 ms ok 122 + groupingsets 1192 ms ok 123 + drop_operator 614 ms ok 124 + password 522 ms ok 125 + identity 3521 ms ok 126 + generated 3680 ms ok 127 + join_hash 4650 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 197 ms ok 129 + brin_multi 562 ms # parallel group (18 tests): async dbsize alter_operator tid tidrangescan tsrf tidscan collate.utf8 create_role alter_generic misc incremental_sort sysviews misc_functions merge create_table_like collate.icu.utf8 without_overlaps ok 130 + create_table_like 1260 ms ok 131 + alter_generic 424 ms ok 132 + alter_operator 163 ms ok 133 + misc 425 ms ok 134 + async 136 ms ok 135 + dbsize 145 ms ok 136 + merge 1087 ms ok 137 + misc_functions 917 ms ok 138 + sysviews 912 ms ok 139 + tsrf 225 ms ok 140 + tid 205 ms ok 141 + tidscan 270 ms ok 142 + tidrangescan 198 ms ok 143 + collate.utf8 274 ms ok 144 + collate.icu.utf8 1822 ms ok 145 + incremental_sort 638 ms ok 146 + create_role 330 ms ok 147 + without_overlaps 1852 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 4410 ms ok 149 + psql 2150 ms ok 150 + psql_crosstab 818 ms ok 151 + amutils 259 ms ok 152 + stats_ext 4812 ms ok 153 + collate.linux.utf8 255 ms ok 154 + collate.windows.win1252 252 ms ok 155 - select_parallel 1281 ms ok 156 - write_parallel 152 ms ok 157 - vacuum_parallel 93 ms # parallel group (2 tests): subscription publication ok 158 + publication 1601 ms ok 159 + subscription 114 ms # parallel group (17 tests): advisory_lock combocid xmlmap portals_p2 equivclass guc indirect_toast dependency tsdicts functional_deps select_views window bitmapops tsearch foreign_data cluster foreign_key ok 160 + select_views 616 ms ok 161 + portals_p2 389 ms ok 162 + foreign_key 9325 ms ok 163 + cluster 3119 ms ok 164 + dependency 545 ms ok 165 + guc 486 ms ok 166 + bitmapops 867 ms ok 167 + combocid 204 ms ok 168 + tsearch 864 ms ok 169 + tsdicts 539 ms ok 170 + foreign_data 1157 ms ok 171 + window 630 ms ok 172 + xmlmap 292 ms ok 173 + functional_deps 541 ms ok 174 + advisory_lock 94 ms ok 175 + indirect_toast 477 ms ok 176 + equivclass 414 ms # parallel group (9 tests): jsonpath jsonpath_encoding json_encoding sqljson sqljson_jsontable json jsonb_jsonpath sqljson_queryfuncs jsonb ok 177 + json 420 ms ok 178 + jsonb 900 ms ok 179 + json_encoding 142 ms ok 180 + jsonpath 115 ms ok 181 + jsonpath_encoding 116 ms ok 182 + jsonb_jsonpath 683 ms ok 183 + sqljson 201 ms ok 184 + sqljson_queryfuncs 802 ms ok 185 + sqljson_jsontable 256 ms # parallel group (18 tests): sequence rowtypes conversion with plancache prepare limit returning polymorphism largeobject xml temp rangefuncs copy2 domain plpgsql truncate alter_table ok 186 + plancache 524 ms ok 187 + limit 603 ms ok 188 + plpgsql 4974 ms ok 189 + copy2 3351 ms ok 190 + temp 1451 ms ok 191 + domain 3923 ms ok 192 + rangefuncs 2050 ms ok 193 + prepare 508 ms ok 194 + conversion 421 ms ok 195 + truncate 4963 ms ok 196 + alter_table 12341 ms ok 197 + sequence 313 ms ok 198 + polymorphism 790 ms ok 199 + rowtypes 304 ms ok 200 + returning 541 ms ok 201 + largeobject 1223 ms ok 202 + with 386 ms ok 203 + xml 1364 ms # parallel group (15 tests): predicate explain hash_part partition_info reloptions memoize compression partition_merge partition_aggregate tuplesort partition_split stats partition_prune partition_join indexing ok 204 + partition_merge 1576 ms ok 205 + partition_split 3206 ms not ok 206 + partition_join 6448 ms ok 207 + partition_prune 5353 ms ok 208 + reloptions 758 ms ok 209 + hash_part 554 ms ok 210 + indexing 6440 ms ok 211 + partition_aggregate 1777 ms ok 212 + partition_info 672 ms ok 213 + tuplesort 3045 ms ok 214 + explain 494 ms ok 215 + compression 1163 ms ok 216 + memoize 798 ms ok 217 + stats 4882 ms ok 218 + predicate 441 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 329 ms ok 220 + event_trigger 947 ms ok 221 - event_trigger_login 52 ms ok 222 - fast_default 1442 ms ok 223 - tablespace 2106 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/partition_join.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out --- /Users/admin/pgsql/src/test/regress/expected/partition_join.out 2024-05-01 15:40:12 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/partition_join.out 2024-05-01 15:43:01 @@ -5133,17 +5133,15 @@ QUERY PLAN ----------------------------------------------------------------------- Limit - -> Merge Append - Sort Key: x.id - -> Merge Left Join - Merge Cond: (x_1.id = y_1.id) + -> Merge Left Join + Merge Cond: (x.id = y.id) + -> Append -> Index Only Scan using fract_t0_pkey on fract_t0 x_1 - -> Index Only Scan using fract_t0_pkey on fract_t0 y_1 - -> Merge Left Join - Merge Cond: (x_2.id = y_2.id) -> Index Only Scan using fract_t1_pkey on fract_t1 x_2 + -> Append + -> Index Only Scan using fract_t0_pkey on fract_t0 y_1 -> Index Only Scan using fract_t1_pkey on fract_t1 y_2 -(11 rows) +(9 rows) EXPLAIN (COSTS OFF) SELECT x.id, y.id FROM fract_t x LEFT JOIN fract_t y USING (id) ORDER BY x.id DESC LIMIT 10; === EOF === [15:43:07.272](76.749s) not ok 5 - regression tests pass [15:43:07.272](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [15:43:07.272](0.000s) # got: '256' # expected: '0' # Checking port 64276 # Found port 64276 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=64276 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/Z2ShTUMOhG Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [15:43:07.280](0.007s) # 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=64275 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/Z2ShTUMOhG dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_D_3D/dump1.sql [15:43:15.766](8.487s) 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/Z2ShTUMOhG -p 64275 -P 64276 --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 [15:43:19.167](3.400s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [15:43:19.167](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/Z2ShTUMOhG -p 64275 -P 64276 --clone --check [15:43:23.818](4.651s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [15:43:23.818](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [15:43:23.818](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 17402 ### 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/Z2ShTUMOhG -p 64275 -P 64276 --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* [15:43:27.528](3.710s) ok 12 - run of pg_upgrade --check for new instance [15:43:27.529](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/Z2ShTUMOhG -p 64275 -P 64276 --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 [15:43:56.297](28.768s) ok 14 - run of pg_upgrade for new instance [15:43:56.297](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 19726 [15:43:56.475](0.178s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=64276 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/Z2ShTUMOhG dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_D_3D/dump2.sql [15:44:08.006](11.531s) ok 17 - dump after running pg_upgrade [15:44:08.122](0.116s) ok 18 - old and new dumps match after pg_upgrade [15:44:08.148](0.026s) 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" [15:44:08.502](0.354s) # Looks like you failed 1 test of 18.