[11:11:39.519](0.008s) # testing using transfer mode --clone # Checking port 59938 # Found port 59938 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=59938 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/aK61l0USa0 Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [11:11:39.528](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_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 6465 [11:11:41.415](1.887s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [11:11:41.611](0.197s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [11:11:41.707](0.096s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [11:11:41.811](0.104s) ok 4 - created database with ASCII characters from 91 to 127 [11:11:41.812](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/aK61l0USa0, port 59938 ok 1 - test_setup 377 ms # parallel group (20 tests): varchar char name oid pg_lsn txid uuid text int2 int4 boolean money regproc float4 int8 bit float8 enum rangetypes numeric ok 2 + boolean 172 ms ok 3 + char 133 ms ok 4 + name 141 ms ok 5 + varchar 118 ms ok 6 + text 157 ms ok 7 + int2 159 ms ok 8 + int4 162 ms ok 9 + int8 179 ms ok 10 + oid 134 ms ok 11 + float4 162 ms ok 12 + float8 171 ms ok 13 + bit 168 ms ok 14 + numeric 724 ms ok 15 + txid 127 ms ok 16 + uuid 129 ms ok 17 + enum 164 ms ok 18 + money 141 ms ok 19 + rangetypes 577 ms ok 20 + pg_lsn 109 ms ok 21 + regproc 134 ms # parallel group (20 tests): path line lseg point circle time timetz macaddr md5 numerology macaddr8 strings inet date interval polygon timestamp timestamptz box multirangetypes ok 22 + strings 218 ms ok 23 + md5 161 ms ok 24 + numerology 181 ms ok 25 + point 91 ms ok 26 + lseg 88 ms ok 27 + line 85 ms ok 28 + box 536 ms ok 29 + path 74 ms ok 30 + polygon 241 ms ok 31 + circle 54 ms ok 32 + date 177 ms ok 33 + time 59 ms ok 34 + timetz 65 ms ok 35 + timestamp 395 ms ok 36 + timestamptz 424 ms ok 37 + interval 174 ms ok 38 + inet 146 ms ok 39 + macaddr 55 ms ok 40 + macaddr8 102 ms ok 41 + multirangetypes 524 ms # parallel group (12 tests): comments unicode xid expressions misc_sanity type_sanity tstypes geometry horology mvcc opr_sanity regex ok 42 + geometry 145 ms ok 43 + horology 154 ms ok 44 + tstypes 135 ms ok 45 + regex 526 ms ok 46 + type_sanity 120 ms ok 47 + opr_sanity 454 ms ok 48 + misc_sanity 69 ms ok 49 + comments 35 ms ok 50 + expressions 52 ms ok 51 + unicode 27 ms ok 52 + xid 33 ms ok 53 + mvcc 134 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 134 ms ok 55 + copyselect 81 ms ok 56 + copydml 88 ms ok 57 + insert 754 ms ok 58 + insert_conflict 440 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_misc create_procedure create_table ok 59 + create_function_c 38 ms ok 60 + create_misc 249 ms ok 61 + create_operator 220 ms ok 62 + create_procedure 249 ms ok 63 + create_table 560 ms ok 64 + create_type 236 ms ok 65 + create_schema 215 ms # parallel group (5 tests): index_including_gist index_including create_view create_index_spgist create_index not ok 66 + create_index 2429 ms ok 67 + create_index_spgist 929 ms ok 68 + create_view 868 ms ok 69 + index_including 763 ms ok 70 + index_including_gist 760 ms # parallel group (16 tests): create_cast hash_func create_aggregate roleattributes errors infinite_recurse typed_table select create_function_sql drop_if_exists create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 326 ms ok 72 + create_function_sql 446 ms ok 73 + create_cast 272 ms ok 74 + constraints 1179 ms ok 75 + triggers 3897 ms ok 76 + select 433 ms ok 77 + inherit 2348 ms ok 78 + typed_table 418 ms ok 79 + vacuum 1027 ms ok 80 + drop_if_exists 462 ms ok 81 + updatable_views 1383 ms ok 82 + roleattributes 307 ms ok 83 + create_am 619 ms ok 84 + hash_func 284 ms ok 85 + errors 297 ms ok 86 + infinite_recurse 298 ms ok 87 - sanity_check 191 ms # parallel group (20 tests): select_distinct_on select_implicit case select_having delete transactions union select_distinct namespace prepared_xacts random portals select_into subselect arrays update aggregates join btree_index hash_index ok 88 + select_into 360 ms ok 89 + select_distinct 208 ms ok 90 + select_distinct_on 95 ms ok 91 + select_implicit 114 ms ok 92 + select_having 134 ms ok 93 + subselect 476 ms ok 94 + union 193 ms ok 95 + case 112 ms ok 96 + join 1271 ms ok 97 + aggregates 1107 ms ok 98 + transactions 166 ms ok 99 + random 229 ms ok 100 + portals 285 ms ok 101 + arrays 464 ms ok 102 + btree_index 1275 ms ok 103 + hash_index 1754 ms ok 104 + update 977 ms ok 105 + delete 110 ms ok 106 + namespace 183 ms ok 107 + prepared_xacts 192 ms # parallel group (20 tests): password tablesample drop_operator init_privs security_label lock collate object_address replica_identity generated groupingsets identity matview rowsecurity spgist gin join_hash brin gist privileges ok 108 + brin 2053 ms ok 109 + gin 1989 ms ok 110 + gist 2070 ms ok 111 + spgist 1809 ms ok 112 + privileges 2369 ms ok 113 + init_privs 618 ms ok 114 + security_label 621 ms ok 115 + collate 709 ms ok 116 + matview 1301 ms ok 117 + lock 622 ms ok 118 + replica_identity 777 ms ok 119 + rowsecurity 1691 ms ok 120 + object_address 698 ms ok 121 + tablesample 485 ms ok 122 + groupingsets 949 ms ok 123 + drop_operator 568 ms ok 124 + password 456 ms ok 125 + identity 961 ms ok 126 + generated 865 ms ok 127 + join_hash 1983 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 68 ms ok 129 + brin_multi 564 ms # parallel group (18 tests): async dbsize collate.utf8 tidrangescan tidscan tsrf alter_operator tid misc create_role misc_functions alter_generic incremental_sort sysviews merge collate.icu.utf8 create_table_like without_overlaps ok 130 + create_table_like 655 ms ok 131 + alter_generic 251 ms ok 132 + alter_operator 161 ms ok 133 + misc 167 ms ok 134 + async 107 ms ok 135 + dbsize 106 ms ok 136 + merge 426 ms ok 137 + misc_functions 236 ms ok 138 + sysviews 343 ms ok 139 + tsrf 135 ms ok 140 + tid 142 ms ok 141 + tidscan 117 ms ok 142 + tidrangescan 108 ms ok 143 + collate.utf8 91 ms ok 144 + collate.icu.utf8 488 ms ok 145 + incremental_sort 213 ms ok 146 + create_role 143 ms ok 147 + without_overlaps 651 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 842 ms ok 149 + psql 809 ms ok 150 + psql_crosstab 209 ms ok 151 + amutils 79 ms ok 152 + stats_ext 1749 ms ok 153 + collate.linux.utf8 62 ms ok 154 + collate.windows.win1252 66 ms ok 155 - select_parallel 945 ms ok 156 - write_parallel 106 ms ok 157 - vacuum_parallel 77 ms # parallel group (2 tests): subscription publication ok 158 + publication 461 ms ok 159 + subscription 80 ms # parallel group (17 tests): portals_p2 advisory_lock functional_deps xmlmap combocid tsdicts equivclass dependency guc select_views indirect_toast cluster window bitmapops tsearch foreign_data foreign_key ok 160 + select_views 323 ms ok 161 + portals_p2 119 ms ok 162 + foreign_key 2034 ms ok 163 + cluster 391 ms ok 164 + dependency 216 ms ok 165 + guc 224 ms ok 166 + bitmapops 670 ms ok 167 + combocid 140 ms ok 168 + tsearch 770 ms ok 169 + tsdicts 138 ms ok 170 + foreign_data 877 ms ok 171 + window 544 ms ok 172 + xmlmap 120 ms ok 173 + functional_deps 113 ms ok 174 + advisory_lock 105 ms ok 175 + indirect_toast 304 ms ok 176 + equivclass 166 ms # parallel group (9 tests): jsonpath_encoding jsonpath sqljson sqljson_jsontable json_encoding sqljson_queryfuncs jsonb_jsonpath json jsonb ok 177 + json 146 ms ok 178 + jsonb 363 ms ok 179 + json_encoding 99 ms ok 180 + jsonpath 55 ms ok 181 + jsonpath_encoding 39 ms ok 182 + jsonb_jsonpath 111 ms ok 183 + sqljson 59 ms ok 184 + sqljson_queryfuncs 89 ms ok 185 + sqljson_jsontable 63 ms # parallel group (18 tests): prepare returning conversion plancache limit copy2 sequence temp largeobject truncate rangefuncs rowtypes with polymorphism domain xml plpgsql alter_table ok 186 + plancache 197 ms ok 187 + limit 198 ms ok 188 + plpgsql 2333 ms ok 189 + copy2 261 ms ok 190 + temp 450 ms ok 191 + domain 609 ms ok 192 + rangefuncs 467 ms ok 193 + prepare 67 ms ok 194 + conversion 105 ms ok 195 + truncate 448 ms ok 196 + alter_table 3119 ms ok 197 + sequence 407 ms ok 198 + polymorphism 534 ms ok 199 + rowtypes 458 ms ok 200 + returning 83 ms ok 201 + largeobject 427 ms ok 202 + with 487 ms ok 203 + xml 2105 ms # parallel group (15 tests): predicate hash_part partition_info reloptions memoize explain compression partition_merge partition_split partition_aggregate stats tuplesort partition_join partition_prune indexing ok 204 + partition_merge 936 ms ok 205 + partition_split 1617 ms ok 206 + partition_join 2236 ms ok 207 + partition_prune 2305 ms ok 208 + reloptions 375 ms ok 209 + hash_part 196 ms ok 210 + indexing 2351 ms ok 211 + partition_aggregate 1716 ms ok 212 + partition_info 326 ms ok 213 + tuplesort 1782 ms ok 214 + explain 394 ms ok 215 + compression 895 ms ok 216 + memoize 380 ms ok 217 + stats 1751 ms ok 218 + predicate 127 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 255 ms ok 220 + event_trigger 470 ms ok 221 - event_trigger_login 51 ms ok 222 - fast_default 196 ms ok 223 - tablespace 2763 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/create_index.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/create_index.out --- /Users/admin/pgsql/src/test/regress/expected/create_index.out 2024-04-12 11:09:41 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/create_index.out 2024-04-12 11:11:48 @@ -2135,11 +2135,19 @@ -- explain (costs off) SELECT unique1 FROM tenk1 WHERE unique1 IN (1, 42, 7) and unique1 = ANY('{7, 8, 9}'); - QUERY PLAN ----------------------------------------------------------------------------------------------------- - Index Only Scan using tenk1_unique1 on tenk1 - Index Cond: ((unique1 = ANY ('{1,42,7}'::integer[])) AND (unique1 = ANY ('{7,8,9}'::integer[]))) -(2 rows) + QUERY PLAN +------------------------------------------------------------------- + Bitmap Heap Scan on tenk1 + Recheck Cond: ((unique1 = 7) OR (unique1 = 8) OR (unique1 = 9)) + Filter: (unique1 = ANY ('{1,42,7}'::integer[])) + -> BitmapOr + -> Bitmap Index Scan on tenk1_unique1 + Index Cond: (unique1 = 7) + -> Bitmap Index Scan on tenk1_unique1 + Index Cond: (unique1 = 8) + -> Bitmap Index Scan on tenk1_unique1 + Index Cond: (unique1 = 9) +(10 rows) SELECT unique1 FROM tenk1 WHERE unique1 IN (1, 42, 7) and unique1 = ANY('{7, 8, 9}'); unique1 @@ -2149,11 +2157,17 @@ explain (costs off) SELECT unique1 FROM tenk1 WHERE unique1 = ANY('{7, 14, 22}') and unique1 = ANY('{33, 44}'::bigint[]); - QUERY PLAN ----------------------------------------------------------------------------------------------------- - Index Only Scan using tenk1_unique1 on tenk1 - Index Cond: ((unique1 = ANY ('{7,14,22}'::integer[])) AND (unique1 = ANY ('{33,44}'::bigint[]))) -(2 rows) + QUERY PLAN +------------------------------------------------------------------------ + Bitmap Heap Scan on tenk1 + Recheck Cond: ((unique1 = '33'::bigint) OR (unique1 = '44'::bigint)) + Filter: (unique1 = ANY ('{7,14,22}'::integer[])) + -> BitmapOr + -> Bitmap Index Scan on tenk1_unique1 + Index Cond: (unique1 = '33'::bigint) + -> Bitmap Index Scan on tenk1_unique1 + Index Cond: (unique1 = '44'::bigint) +(8 rows) SELECT unique1 FROM tenk1 WHERE unique1 = ANY('{7, 14, 22}') and unique1 = ANY('{33, 44}'::bigint[]); unique1 === EOF === [11:12:16.161](34.350s) not ok 5 - regression tests pass [11:12:16.162](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [11:12:16.162](0.000s) # got: '256' # expected: '0' # Checking port 59939 # Found port 59939 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=59939 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/aK61l0USa0 Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [11:12:16.171](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=59938 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/aK61l0USa0 dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_o7WS/dump1.sql [11:12:22.280](6.109s) 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/aK61l0USa0 -p 59938 -P 59939 --clone --check check for "/Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin/does/not/exist" failed: No such file or directory Failure, exiting [11:12:23.130](0.850s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [11:12:23.130](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/aK61l0USa0 -p 59938 -P 59939 --clone --check [11:12:24.779](1.649s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [11:12:24.779](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [11:12:24.779](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 15457 ### 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/aK61l0USa0 -p 59938 -P 59939 --clone --check Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage ok Checking for presence of required libraries ok Checking database user is the install user ok Checking for prepared transactions ok Checking for new cluster tablespace directories ok *Clusters are compatible* [11:12:27.122](2.343s) ok 12 - run of pg_upgrade --check for new instance [11:12:27.122](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/aK61l0USa0 -p 59938 -P 59939 --clone Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state ok Checking for data type usage ok Creating dump of global objects ok Creating dump of database schemas ok Checking for presence of required libraries ok Checking database user is the install user ok Checking for prepared transactions ok Checking for new cluster tablespace directories ok If pg_upgrade fails after this point, you must re-initdb the new cluster before continuing. Performing Upgrade ------------------ Setting locale and encoding for new cluster ok Analyzing all rows in the new cluster ok Freezing all rows in the new cluster ok Deleting files from new pg_xact ok Copying old pg_xact to new server ok Setting oldest XID for new cluster ok Setting next transaction ID and epoch for new cluster ok Deleting files from new pg_multixact/offsets ok Copying old pg_multixact/offsets to new server ok Deleting files from new pg_multixact/members ok Copying old pg_multixact/members to new server ok Setting next multixact ID and offset for new cluster ok Resetting WAL archives ok Setting frozenxid and minmxid counters in new cluster ok Restoring global objects in the new cluster ok Restoring database schemas in the new cluster ok Cloning user relation files ok Setting next OID for new cluster ok Creating script to delete old cluster ok Checking for extension updates ok Upgrade Complete ---------------- Optimizer statistics are not transferred by pg_upgrade. Once you start the new server, consider running: /Users/admin/pgsql/build/tmp_install/usr/local/pgsql/bin/vacuumdb --all --analyze-in-stages Running this script will delete the old cluster's data files: ./delete_old_cluster.sh [11:12:44.697](17.575s) ok 14 - run of pg_upgrade for new instance [11:12:44.698](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 19075 [11:12:45.406](0.708s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=59939 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/aK61l0USa0 dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_o7WS/dump2.sql [11:12:55.079](9.673s) ok 17 - dump after running pg_upgrade [11:12:55.212](0.133s) ok 18 - old and new dumps match after pg_upgrade [11:12:55.212](0.000s) 1..18 ### Stopping node "new_node" using mode immediate # Running: pg_ctl -D /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -m immediate stop waiting for server to shut down.... done server stopped # No postmaster PID for node "new_node" [11:12:55.320](0.108s) # Looks like you failed 1 test of 18.