[17:56:02.919](0.033s) # testing using transfer mode --clone # Checking port 50953 # Found port 50953 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=50953 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/3IIZIviNwG Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [17:56:02.933](0.014s) # 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 9752 [17:56:05.199](2.265s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [17:56:05.640](0.441s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [17:56:05.736](0.096s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [17:56:05.902](0.166s) ok 4 - created database with ASCII characters from 91 to 127 [17:56:05.902](0.000s) # running regression tests in old instance # using postmaster on /var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/3IIZIviNwG, port 50953 ok 1 - test_setup 504 ms # parallel group (20 tests): varchar char boolean float4 float8 name oid int2 txid int4 bit int8 text pg_lsn uuid regproc money enum rangetypes numeric ok 2 + boolean 212 ms ok 3 + char 178 ms ok 4 + name 315 ms ok 5 + varchar 162 ms ok 6 + text 337 ms ok 7 + int2 319 ms ok 8 + int4 323 ms ok 9 + int8 326 ms ok 10 + oid 301 ms ok 11 + float4 193 ms ok 12 + float8 215 ms ok 13 + bit 305 ms ok 14 + numeric 1034 ms ok 15 + txid 293 ms ok 16 + uuid 309 ms ok 17 + enum 330 ms ok 18 + money 307 ms ok 19 + rangetypes 825 ms ok 20 + pg_lsn 285 ms ok 21 + regproc 288 ms # parallel group (20 tests): timetz time inet macaddr interval numerology date macaddr8 md5 lseg point line circle path strings timestamp polygon box timestamptz multirangetypes ok 22 + strings 336 ms ok 23 + md5 168 ms ok 24 + numerology 129 ms ok 25 + point 178 ms ok 26 + lseg 168 ms ok 27 + line 176 ms ok 28 + box 476 ms ok 29 + path 203 ms ok 30 + polygon 417 ms ok 31 + circle 163 ms ok 32 + date 109 ms ok 33 + time 44 ms ok 34 + timetz 42 ms ok 35 + timestamp 365 ms ok 36 + timestamptz 567 ms ok 37 + interval 72 ms ok 38 + inet 43 ms ok 39 + macaddr 20 ms ok 40 + macaddr8 68 ms ok 41 + multirangetypes 554 ms # parallel group (12 tests): misc_sanity comments mvcc unicode expressions xid geometry horology tstypes type_sanity regex opr_sanity ok 42 + geometry 204 ms ok 43 + horology 210 ms ok 44 + tstypes 212 ms ok 45 + regex 456 ms ok 46 + type_sanity 262 ms ok 47 + opr_sanity 511 ms ok 48 + misc_sanity 65 ms ok 49 + comments 65 ms ok 50 + expressions 163 ms ok 51 + unicode 85 ms ok 52 + xid 162 ms ok 53 + mvcc 78 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 581 ms ok 55 + copyselect 315 ms ok 56 + copydml 85 ms ok 57 + insert 1481 ms ok 58 + insert_conflict 1091 ms # parallel group (7 tests): create_function_c create_schema create_type create_procedure create_operator create_misc create_table ok 59 + create_function_c 58 ms ok 60 + create_misc 145 ms ok 61 + create_operator 137 ms ok 62 + create_procedure 135 ms ok 63 + create_table 816 ms ok 64 + create_type 124 ms ok 65 + create_schema 118 ms # parallel group (5 tests): index_including_gist create_index_spgist index_including create_view create_index ok 66 + create_index 3539 ms ok 67 + create_index_spgist 916 ms ok 68 + create_view 1707 ms ok 69 + index_including 919 ms ok 70 + index_including_gist 859 ms # parallel group (16 tests): create_cast create_aggregate errors hash_func roleattributes drop_if_exists create_function_sql select typed_table infinite_recurse create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 154 ms ok 72 + create_function_sql 240 ms ok 73 + create_cast 99 ms ok 74 + constraints 1337 ms ok 75 + triggers 3410 ms ok 76 + select 278 ms ok 77 + inherit 2520 ms ok 78 + typed_table 307 ms ok 79 + vacuum 877 ms ok 80 + drop_if_exists 159 ms ok 81 + updatable_views 2422 ms ok 82 + roleattributes 142 ms ok 83 + create_am 458 ms ok 84 + hash_func 125 ms ok 85 + errors 121 ms ok 86 + infinite_recurse 445 ms ok 87 - sanity_check 113 ms # parallel group (20 tests): delete random case namespace prepared_xacts select_distinct_on select_implicit select_having select_into select_distinct union subselect transactions portals arrays hash_index update aggregates join btree_index ok 88 + select_into 202 ms ok 89 + select_distinct 215 ms ok 90 + select_distinct_on 169 ms ok 91 + select_implicit 177 ms ok 92 + select_having 178 ms ok 93 + subselect 253 ms ok 94 + union 243 ms ok 95 + case 115 ms ok 96 + join 1680 ms ok 97 + aggregates 1454 ms ok 98 + transactions 733 ms ok 99 + random 94 ms ok 100 + portals 770 ms ok 101 + arrays 1109 ms ok 102 + btree_index 2005 ms ok 103 + hash_index 1168 ms ok 104 + update 1212 ms ok 105 + delete 54 ms ok 106 + namespace 88 ms ok 107 + prepared_xacts 105 ms # parallel group (20 tests): init_privs drop_operator security_label lock tablesample password object_address collate replica_identity groupingsets identity matview spgist gin gist generated rowsecurity join_hash brin privileges ok 108 + brin 4576 ms ok 109 + gin 2196 ms ok 110 + gist 2334 ms ok 111 + spgist 2113 ms ok 112 + privileges 5242 ms ok 113 + init_privs 217 ms ok 114 + security_label 699 ms ok 115 + collate 997 ms ok 116 + matview 1803 ms ok 117 + lock 697 ms ok 118 + replica_identity 1054 ms ok 119 + rowsecurity 2870 ms ok 120 + object_address 971 ms ok 121 + tablesample 690 ms ok 122 + groupingsets 1106 ms ok 123 + drop_operator 327 ms ok 124 + password 687 ms ok 125 + identity 1365 ms ok 126 + generated 2355 ms ok 127 + join_hash 4484 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 86 ms ok 129 + brin_multi 360 ms # parallel group (18 tests): async dbsize collate.utf8 tid alter_operator tidscan misc tidrangescan create_role incremental_sort tsrf sysviews misc_functions alter_generic collate.icu.utf8 merge create_table_like without_overlaps ok 130 + create_table_like 1205 ms ok 131 + alter_generic 973 ms ok 132 + alter_operator 651 ms ok 133 + misc 673 ms ok 134 + async 164 ms ok 135 + dbsize 564 ms ok 136 + merge 1145 ms ok 137 + misc_functions 869 ms ok 138 + sysviews 786 ms ok 139 + tsrf 752 ms ok 140 + tid 612 ms ok 141 + tidscan 615 ms ok 142 + tidrangescan 676 ms ok 143 + collate.utf8 559 ms ok 144 + collate.icu.utf8 1046 ms ok 145 + incremental_sort 704 ms ok 146 + create_role 669 ms ok 147 + without_overlaps 1194 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 3425 ms ok 149 + psql 2443 ms ok 150 + psql_crosstab 104 ms ok 151 + amutils 67 ms ok 152 + stats_ext 4133 ms ok 153 + collate.linux.utf8 50 ms ok 154 + collate.windows.win1252 46 ms ok 155 - select_parallel 1073 ms ok 156 - write_parallel 245 ms ok 157 - vacuum_parallel 108 ms # parallel group (2 tests): subscription publication ok 158 + publication 3186 ms ok 159 + subscription 262 ms # parallel group (17 tests): portals_p2 advisory_lock select_views tsdicts xmlmap combocid indirect_toast guc functional_deps window equivclass dependency bitmapops tsearch foreign_data cluster foreign_key ok 160 + select_views 542 ms ok 161 + portals_p2 63 ms ok 162 + foreign_key 9081 ms ok 163 + cluster 3877 ms ok 164 + dependency 1137 ms ok 165 + guc 980 ms ok 166 + bitmapops 1400 ms ok 167 + combocid 961 ms ok 168 + tsearch 1906 ms ok 169 + tsdicts 652 ms ok 170 + foreign_data 2237 ms ok 171 + window 1016 ms ok 172 + xmlmap 754 ms ok 173 + functional_deps 965 ms ok 174 + advisory_lock 463 ms ok 175 + indirect_toast 938 ms ok 176 + equivclass 1030 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson_queryfuncs sqljson json jsonb_jsonpath jsonb ok 177 + json 298 ms ok 178 + jsonb 538 ms ok 179 + json_encoding 89 ms ok 180 + jsonpath 197 ms ok 181 + jsonpath_encoding 75 ms ok 182 + jsonb_jsonpath 310 ms ok 183 + sqljson 249 ms ok 184 + sqljson_queryfuncs 234 ms ok 185 + sqljson_jsontable 93 ms # parallel group (18 tests): limit prepare returning temp rowtypes plancache conversion polymorphism with copy2 sequence largeobject rangefuncs truncate domain xml plpgsql alter_table ok 186 + plancache 690 ms ok 187 + limit 246 ms ok 188 + plpgsql 2207 ms ok 189 + copy2 1131 ms ok 190 + temp 330 ms ok 191 + domain 1557 ms ok 192 + rangefuncs 1202 ms ok 193 + prepare 248 ms ok 194 + conversion 963 ms ok 195 + truncate 1259 ms not ok 196 + alter_table 10171 ms ok 197 + sequence 1116 ms ok 198 + polymorphism 957 ms ok 199 + rowtypes 341 ms ok 200 + returning 245 ms ok 201 + largeobject 1143 ms ok 202 + with 993 ms ok 203 + xml 1941 ms # parallel group (15 tests): predicate hash_part explain partition_info reloptions memoize partition_aggregate tuplesort compression partition_merge partition_split stats partition_prune partition_join indexing ok 204 + partition_merge 4913 ms ok 205 + partition_split 5048 ms ok 206 + partition_join 6951 ms ok 207 + partition_prune 6476 ms ok 208 + reloptions 2038 ms ok 209 + hash_part 820 ms ok 210 + indexing 6986 ms ok 211 + partition_aggregate 2277 ms ok 212 + partition_info 1174 ms ok 213 + tuplesort 2860 ms ok 214 + explain 1051 ms ok 215 + compression 2918 ms ok 216 + memoize 2180 ms ok 217 + stats 5670 ms ok 218 + predicate 651 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 283 ms ok 220 + event_trigger 572 ms ok 221 - event_trigger_login 51 ms ok 222 - fast_default 1333 ms ok 223 - tablespace 7471 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-04-16 17:54:35 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-16 17:57: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 +-------+------------+---------------+-------------+---------------------- + 37893 | | 0 | 37893 | pktable_pkey + 37890 | | 0 | 37890 | pktable + 37896 | | 0 | 37896 | fktable + 38416 | | 0 | 38421 | foo + 38425 | | 0 | 38425 | pg_toast_38416_index + 38424 | | 0 | 38424 | pg_toast_38416 + 38612 | | 0 | 38612 | old_oids + 38629 | | 0 | 38629 | pg_toast_38626 + 38630 | | 0 | 38630 | pg_toast_38626_index + 38626 | | 0 | 38626 | recur2 + 38621 | | 0 | 38621 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [17:57:22.267](76.365s) not ok 5 - regression tests pass [17:57:22.269](0.001s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [17:57:22.269](0.000s) # got: '256' # expected: '0' # Checking port 50954 # Found port 50954 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=50954 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/3IIZIviNwG Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [17:57:22.277](0.008s) # 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=50953 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/3IIZIviNwG dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_qyeP/dump1.sql [17:57:29.165](6.888s) 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/3IIZIviNwG -p 50953 -P 50954 --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 [17:57:30.153](0.988s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [17:57:30.154](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/3IIZIviNwG -p 50953 -P 50954 --clone --check [17:57:35.691](5.537s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [17:57:35.691](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [17:57:35.691](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 21574 ### 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/3IIZIviNwG -p 50953 -P 50954 --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* [17:57:39.505](3.814s) ok 12 - run of pg_upgrade --check for new instance [17:57:39.505](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/3IIZIviNwG -p 50953 -P 50954 --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 [17:58:17.800](38.294s) ok 14 - run of pg_upgrade for new instance [17:58:17.800](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 24394 [17:58:17.951](0.151s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=50954 host=/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/3IIZIviNwG dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_qyeP/dump2.sql [17:58:27.764](9.813s) ok 17 - dump after running pg_upgrade [17:58:28.292](0.528s) ok 18 - old and new dumps match after pg_upgrade [17:58:28.293](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" [17:58:28.530](0.237s) # Looks like you failed 1 test of 18.