[05:19:02.496](0.014s) # testing using transfer mode --clone # Checking port 61636 # Found port 61636 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=61636 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/nKsBHWfhqw Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [05:19:02.514](0.018s) # 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 9829 [05:19:04.568](2.054s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [05:19:05.249](0.681s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [05:19:05.422](0.173s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [05:19:05.537](0.115s) ok 4 - created database with ASCII characters from 91 to 127 [05:19:05.539](0.001s) # running regression tests in old instance # using postmaster on /var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/nKsBHWfhqw, port 61636 ok 1 - test_setup 387 ms # parallel group (20 tests): varchar char name oid pg_lsn txid uuid text int2 int4 float4 money boolean regproc enum bit int8 float8 rangetypes numeric ok 2 + boolean 151 ms ok 3 + char 102 ms ok 4 + name 109 ms ok 5 + varchar 93 ms ok 6 + text 128 ms ok 7 + int2 127 ms ok 8 + int4 133 ms ok 9 + int8 172 ms ok 10 + oid 98 ms ok 11 + float4 131 ms ok 12 + float8 171 ms ok 13 + bit 155 ms ok 14 + numeric 781 ms ok 15 + txid 90 ms ok 16 + uuid 92 ms ok 17 + enum 138 ms ok 18 + money 109 ms ok 19 + rangetypes 752 ms ok 20 + pg_lsn 73 ms ok 21 + regproc 105 ms # parallel group (20 tests): timetz time circle path macaddr macaddr8 inet date md5 interval lseg line point numerology strings timestamp box timestamptz polygon multirangetypes ok 22 + strings 394 ms ok 23 + md5 141 ms ok 24 + numerology 192 ms ok 25 + point 176 ms ok 26 + lseg 167 ms ok 27 + line 171 ms ok 28 + box 437 ms ok 29 + path 74 ms ok 30 + polygon 529 ms ok 31 + circle 69 ms ok 32 + date 111 ms ok 33 + time 64 ms ok 34 + timetz 59 ms ok 35 + timestamp 385 ms ok 36 + timestamptz 387 ms ok 37 + interval 90 ms ok 38 + inet 64 ms ok 39 + macaddr 41 ms ok 40 + macaddr8 52 ms ok 41 + multirangetypes 571 ms # parallel group (12 tests): misc_sanity comments unicode type_sanity xid expressions mvcc tstypes horology geometry opr_sanity regex ok 42 + geometry 323 ms ok 43 + horology 311 ms ok 44 + tstypes 267 ms ok 45 + regex 560 ms ok 46 + type_sanity 171 ms ok 47 + opr_sanity 358 ms ok 48 + misc_sanity 82 ms ok 49 + comments 82 ms ok 50 + expressions 170 ms ok 51 + unicode 93 ms ok 52 + xid 159 ms ok 53 + mvcc 220 ms # parallel group (5 tests): copydml copyselect insert_conflict copy insert ok 54 + copy 542 ms ok 55 + copyselect 297 ms ok 56 + copydml 257 ms ok 57 + insert 1210 ms ok 58 + insert_conflict 521 ms # parallel group (7 tests): create_function_c create_schema create_operator create_type create_misc create_procedure create_table ok 59 + create_function_c 49 ms ok 60 + create_misc 421 ms ok 61 + create_operator 312 ms ok 62 + create_procedure 430 ms ok 63 + create_table 1153 ms ok 64 + create_type 330 ms ok 65 + create_schema 292 ms # parallel group (5 tests): create_index_spgist index_including_gist index_including create_view create_index ok 66 + create_index 2559 ms ok 67 + create_index_spgist 493 ms ok 68 + create_view 1630 ms ok 69 + index_including 1566 ms ok 70 + index_including_gist 1501 ms # parallel group (16 tests): create_cast hash_func create_aggregate roleattributes errors drop_if_exists typed_table select create_function_sql create_am infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 144 ms ok 72 + create_function_sql 216 ms ok 73 + create_cast 102 ms ok 74 + constraints 1407 ms ok 75 + triggers 2939 ms ok 76 + select 200 ms ok 77 + inherit 2101 ms ok 78 + typed_table 174 ms ok 79 + vacuum 735 ms ok 80 + drop_if_exists 146 ms ok 81 + updatable_views 1913 ms ok 82 + roleattributes 125 ms ok 83 + create_am 213 ms ok 84 + hash_func 110 ms ok 85 + errors 115 ms ok 86 + infinite_recurse 439 ms ok 87 - sanity_check 84 ms # parallel group (20 tests): select_distinct_on random prepared_xacts select_having delete select_into case namespace select_implicit select_distinct arrays portals union transactions subselect update btree_index aggregates hash_index join ok 88 + select_into 247 ms ok 89 + select_distinct 316 ms ok 90 + select_distinct_on 100 ms ok 91 + select_implicit 261 ms ok 92 + select_having 190 ms ok 93 + subselect 618 ms ok 94 + union 518 ms ok 95 + case 237 ms ok 96 + join 1788 ms ok 97 + aggregates 1382 ms ok 98 + transactions 506 ms ok 99 + random 106 ms ok 100 + portals 495 ms ok 101 + arrays 382 ms ok 102 + btree_index 1301 ms ok 103 + hash_index 1755 ms ok 104 + update 827 ms ok 105 + delete 171 ms ok 106 + namespace 202 ms ok 107 + prepared_xacts 140 ms # parallel group (20 tests): init_privs security_label drop_operator lock password tablesample object_address collate spgist groupingsets gin gist replica_identity identity matview rowsecurity generated join_hash brin privileges ok 108 + brin 5695 ms ok 109 + gin 2389 ms ok 110 + gist 2436 ms ok 111 + spgist 2256 ms ok 112 + privileges 6630 ms ok 113 + init_privs 229 ms ok 114 + security_label 366 ms ok 115 + collate 2008 ms ok 116 + matview 2992 ms ok 117 + lock 382 ms ok 118 + replica_identity 2426 ms ok 119 + rowsecurity 3149 ms ok 120 + object_address 1790 ms ok 121 + tablesample 887 ms ok 122 + groupingsets 2233 ms ok 123 + drop_operator 345 ms ok 124 + password 369 ms ok 125 + identity 2827 ms ok 126 + generated 3183 ms ok 127 + join_hash 5127 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 108 ms ok 129 + brin_multi 353 ms # parallel group (18 tests): async dbsize collate.utf8 tid tidrangescan tidscan alter_operator misc tsrf sysviews misc_functions alter_generic create_role create_table_like incremental_sort collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 819 ms ok 131 + alter_generic 746 ms ok 132 + alter_operator 472 ms ok 133 + misc 490 ms ok 134 + async 108 ms ok 135 + dbsize 122 ms ok 136 + merge 1562 ms ok 137 + misc_functions 677 ms ok 138 + sysviews 488 ms ok 139 + tsrf 479 ms ok 140 + tid 159 ms ok 141 + tidscan 161 ms ok 142 + tidrangescan 159 ms ok 143 + collate.utf8 117 ms ok 144 + collate.icu.utf8 1502 ms ok 145 + incremental_sort 800 ms ok 146 + create_role 751 ms ok 147 + without_overlaps 1716 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 2316 ms ok 149 + psql 1587 ms ok 150 + psql_crosstab 184 ms ok 151 + amutils 59 ms ok 152 + stats_ext 2538 ms ok 153 + collate.linux.utf8 50 ms ok 154 + collate.windows.win1252 49 ms ok 155 - select_parallel 973 ms ok 156 - write_parallel 154 ms ok 157 - vacuum_parallel 102 ms # parallel group (2 tests): subscription publication ok 158 + publication 2206 ms ok 159 + subscription 150 ms # parallel group (17 tests): advisory_lock xmlmap functional_deps equivclass tsdicts combocid window portals_p2 indirect_toast guc bitmapops select_views dependency tsearch foreign_data cluster foreign_key ok 160 + select_views 1298 ms ok 161 + portals_p2 189 ms ok 162 + foreign_key 10373 ms ok 163 + cluster 4152 ms ok 164 + dependency 1312 ms ok 165 + guc 1138 ms ok 166 + bitmapops 1165 ms ok 167 + combocid 101 ms ok 168 + tsearch 1665 ms ok 169 + tsdicts 76 ms ok 170 + foreign_data 1803 ms ok 171 + window 134 ms ok 172 + xmlmap 51 ms ok 173 + functional_deps 51 ms ok 174 + advisory_lock 42 ms ok 175 + indirect_toast 240 ms ok 176 + equivclass 58 ms # parallel group (9 tests): jsonpath_encoding json_encoding jsonpath sqljson sqljson_jsontable sqljson_queryfuncs jsonb_jsonpath json jsonb ok 177 + json 685 ms ok 178 + jsonb 862 ms ok 179 + json_encoding 304 ms ok 180 + jsonpath 334 ms ok 181 + jsonpath_encoding 298 ms ok 182 + jsonb_jsonpath 666 ms ok 183 + sqljson 395 ms ok 184 + sqljson_queryfuncs 584 ms ok 185 + sqljson_jsontable 472 ms # parallel group (18 tests): prepare returning limit largeobject polymorphism plancache xml rowtypes conversion temp with sequence copy2 rangefuncs truncate domain plpgsql alter_table ok 186 + plancache 1166 ms ok 187 + limit 602 ms ok 188 + plpgsql 3708 ms ok 189 + copy2 2156 ms ok 190 + temp 1603 ms ok 191 + domain 2619 ms ok 192 + rangefuncs 2158 ms ok 193 + prepare 231 ms ok 194 + conversion 1480 ms ok 195 + truncate 2447 ms not ok 196 + alter_table 12117 ms ok 197 + sequence 2024 ms ok 198 + polymorphism 848 ms ok 199 + rowtypes 1353 ms ok 200 + returning 361 ms ok 201 + largeobject 760 ms ok 202 + with 1859 ms ok 203 + xml 1039 ms # parallel group (15 tests): predicate hash_part explain reloptions partition_info memoize tuplesort compression partition_aggregate partition_merge stats partition_split partition_prune partition_join indexing ok 204 + partition_merge 6462 ms ok 205 + partition_split 7975 ms ok 206 + partition_join 15108 ms ok 207 + partition_prune 14539 ms ok 208 + reloptions 692 ms ok 209 + hash_part 362 ms ok 210 + indexing 15269 ms ok 211 + partition_aggregate 3548 ms ok 212 + partition_info 1468 ms ok 213 + tuplesort 2099 ms ok 214 + explain 650 ms ok 215 + compression 2811 ms ok 216 + memoize 1540 ms ok 217 + stats 6741 ms ok 218 + predicate 289 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 408 ms ok 220 + event_trigger 528 ms ok 221 - event_trigger_login 173 ms ok 222 - fast_default 1668 ms ok 223 - tablespace 3235 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/alter_table.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out --- /Users/admin/pgsql/src/test/regress/expected/alter_table.out 2024-05-05 05:17:41 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-05-05 05:20:04 @@ -3476,9 +3476,20 @@ WHERE relkind IN ('r', 'i', 'S', 't', 'm') AND mapped_oid IS DISTINCT FROM oid; SELECT m.* FROM filenode_mapping m LEFT JOIN pg_class c ON c.oid = m.oid WHERE c.oid IS NOT NULL OR m.mapped_oid IS NOT NULL; - oid | mapped_oid | reltablespace | relfilenode | relname ------+------------+---------------+-------------+--------- -(0 rows) + oid | mapped_oid | reltablespace | relfilenode | relname +-------+------------+---------------+-------------+---------------------- + 37765 | | 0 | 37765 | pktable_pkey + 37759 | | 0 | 37759 | pktable + 37767 | | 0 | 37767 | fktable + 38477 | | 0 | 38482 | foo + 38486 | | 0 | 38486 | pg_toast_38477_index + 38485 | | 0 | 38485 | pg_toast_38477 + 38726 | | 0 | 38726 | pg_toast_38723 + 38727 | | 0 | 38727 | pg_toast_38723_index + 38723 | | 0 | 38723 | recur2 + 38718 | | 0 | 38718 | recur1 + 38709 | | 0 | 38709 | old_oids +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [05:20:31.776](86.237s) not ok 5 - regression tests pass [05:20:31.776](0.001s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [05:20:31.777](0.000s) # got: '256' # expected: '0' # Checking port 61637 # Found port 61637 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=61637 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/nKsBHWfhqw Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [05:20:31.785](0.009s) # 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=61636 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/nKsBHWfhqw dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_I2wr/dump1.sql [05:20:37.977](6.192s) 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/nKsBHWfhqw -p 61636 -P 61637 --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:20:43.512](5.535s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [05:20:43.512](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/nKsBHWfhqw -p 61636 -P 61637 --clone --check [05:20:48.510](4.998s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [05:20:48.511](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [05:20:48.511](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 22066 ### 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/nKsBHWfhqw -p 61636 -P 61637 --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:21:01.108](12.597s) ok 12 - run of pg_upgrade --check for new instance [05:21:01.108](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/nKsBHWfhqw -p 61636 -P 61637 --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:21:39.929](38.821s) ok 14 - run of pg_upgrade for new instance [05:21:39.929](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 26634 [05:21:40.119](0.190s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=61637 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/nKsBHWfhqw dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_I2wr/dump2.sql [05:22:16.451](36.332s) ok 17 - dump after running pg_upgrade [05:22:16.854](0.402s) ok 18 - old and new dumps match after pg_upgrade [05:22:16.854](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" [05:22:16.981](0.127s) # Looks like you failed 1 test of 18.