[19:31:36.903](0.013s) # testing using transfer mode --clone # Checking port 64268 # Found port 64268 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=64268 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/bsrFPucftd Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [19:31:36.952](0.049s) # 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 --locale C --locale-provider icu --icu-locale fr-CA The files belonging to this database system will be owned by user "admin". This user must also own the server process. Using language tag "fr-CA" for ICU locale "fr-CA". The database cluster will be initialized with this locale configuration: provider: icu ICU locale: fr-CA LC_COLLATE: C LC_CTYPE: C LC_MESSAGES: C LC_MONETARY: C LC_NUMERIC: C LC_TIME: C 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 8367 [19:31:38.636](1.684s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [19:31:38.809](0.173s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [19:31:39.024](0.215s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [19:31:39.193](0.168s) ok 4 - created database with ASCII characters from 91 to 127 [19:31:39.193](0.000s) # running regression tests in old instance # using postmaster on /var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/bsrFPucftd, port 64268 ok 1 - test_setup 587 ms # parallel group (20 tests): varchar char name int2 text boolean oid int4 int8 float4 float8 bit txid uuid pg_lsn regproc money enum numeric rangetypes ok 2 + boolean 109 ms ok 3 + char 95 ms ok 4 + name 94 ms ok 5 + varchar 89 ms ok 6 + text 95 ms ok 7 + int2 93 ms ok 8 + int4 103 ms ok 9 + int8 113 ms ok 10 + oid 95 ms ok 11 + float4 112 ms ok 12 + float8 114 ms ok 13 + bit 112 ms ok 14 + numeric 554 ms ok 15 + txid 113 ms ok 16 + uuid 121 ms ok 17 + enum 266 ms ok 18 + money 208 ms ok 19 + rangetypes 626 ms ok 20 + pg_lsn 107 ms ok 21 + regproc 194 ms # parallel group (20 tests): macaddr8 macaddr md5 path lseg circle point line time timetz inet interval date numerology strings polygon multirangetypes box timestamp timestamptz ok 22 + strings 298 ms ok 23 + md5 178 ms ok 24 + numerology 252 ms ok 25 + point 206 ms ok 26 + lseg 190 ms ok 27 + line 204 ms ok 28 + box 479 ms ok 29 + path 172 ms ok 30 + polygon 294 ms ok 31 + circle 170 ms ok 32 + date 212 ms ok 33 + time 185 ms ok 34 + timetz 187 ms ok 35 + timestamp 505 ms ok 36 + timestamptz 607 ms ok 37 + interval 191 ms ok 38 + inet 181 ms ok 39 + macaddr 53 ms ok 40 + macaddr8 44 ms ok 41 + multirangetypes 357 ms # parallel group (12 tests): comments misc_sanity xid unicode expressions mvcc horology tstypes geometry type_sanity opr_sanity regex ok 42 + geometry 226 ms ok 43 + horology 181 ms ok 44 + tstypes 200 ms ok 45 + regex 394 ms ok 46 + type_sanity 247 ms ok 47 + opr_sanity 380 ms ok 48 + misc_sanity 78 ms ok 49 + comments 76 ms ok 50 + expressions 124 ms ok 51 + unicode 108 ms ok 52 + xid 103 ms ok 53 + mvcc 128 ms # parallel group (5 tests): copyselect copydml copy insert insert_conflict ok 54 + copy 374 ms ok 55 + copyselect 242 ms ok 56 + copydml 246 ms ok 57 + insert 696 ms ok 58 + insert_conflict 702 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 35 ms ok 60 + create_misc 250 ms ok 61 + create_operator 243 ms ok 62 + create_procedure 269 ms ok 63 + create_table 847 ms ok 64 + create_type 257 ms ok 65 + create_schema 211 ms # parallel group (5 tests): create_index_spgist index_including_gist index_including create_view create_index ok 66 + create_index 2816 ms ok 67 + create_index_spgist 905 ms ok 68 + create_view 1377 ms ok 69 + index_including 1080 ms ok 70 + index_including_gist 960 ms # parallel group (16 tests): hash_func roleattributes errors create_cast select create_aggregate drop_if_exists create_function_sql typed_table infinite_recurse create_am constraints vacuum updatable_views inherit triggers ok 71 + create_aggregate 171 ms ok 72 + create_function_sql 257 ms ok 73 + create_cast 164 ms ok 74 + constraints 1362 ms ok 75 + triggers 3422 ms ok 76 + select 163 ms ok 77 + inherit 2794 ms ok 78 + typed_table 278 ms ok 79 + vacuum 1485 ms ok 80 + drop_if_exists 158 ms ok 81 + updatable_views 2118 ms ok 82 + roleattributes 114 ms ok 83 + create_am 947 ms ok 84 + hash_func 81 ms ok 85 + errors 109 ms ok 86 + infinite_recurse 298 ms ok 87 - sanity_check 199 ms # parallel group (20 tests): select_distinct_on select_having random delete namespace select_implicit case select_into prepared_xacts select_distinct union transactions subselect portals arrays update aggregates btree_index join hash_index ok 88 + select_into 336 ms ok 89 + select_distinct 502 ms ok 90 + select_distinct_on 70 ms ok 91 + select_implicit 216 ms ok 92 + select_having 97 ms ok 93 + subselect 626 ms ok 94 + union 528 ms ok 95 + case 225 ms ok 96 + join 2150 ms ok 97 + aggregates 1703 ms ok 98 + transactions 596 ms ok 99 + random 112 ms ok 100 + portals 781 ms ok 101 + arrays 780 ms ok 102 + btree_index 1936 ms ok 103 + hash_index 2762 ms ok 104 + update 1412 ms ok 105 + delete 150 ms ok 106 + namespace 146 ms ok 107 + prepared_xacts 298 ms # parallel group (20 tests): drop_operator tablesample password init_privs security_label lock object_address collate replica_identity groupingsets matview identity spgist brin rowsecurity generated gist gin join_hash privileges ok 108 + brin 1786 ms ok 109 + gin 2128 ms ok 110 + gist 2050 ms ok 111 + spgist 1551 ms ok 112 + privileges 2989 ms ok 113 + init_privs 292 ms ok 114 + security_label 300 ms ok 115 + collate 768 ms ok 116 + matview 1023 ms ok 117 + lock 305 ms ok 118 + replica_identity 786 ms ok 119 + rowsecurity 1786 ms ok 120 + object_address 320 ms ok 121 + tablesample 120 ms ok 122 + groupingsets 846 ms ok 123 + drop_operator 60 ms ok 124 + password 114 ms ok 125 + identity 1093 ms ok 126 + generated 1804 ms ok 127 + join_hash 2764 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 69 ms ok 129 + brin_multi 1016 ms # parallel group (17 tests): async dbsize tid tidrangescan tidscan alter_operator tsrf misc misc_functions create_role alter_generic incremental_sort without_overlaps sysviews collate.icu.utf8 merge create_table_like ok 130 + create_table_like 764 ms ok 131 + alter_generic 282 ms ok 132 + alter_operator 103 ms ok 133 + misc 115 ms ok 134 + async 54 ms ok 135 + dbsize 66 ms ok 136 + merge 748 ms ok 137 + misc_functions 199 ms ok 138 + sysviews 398 ms ok 139 + tsrf 94 ms ok 140 + tid 78 ms ok 141 + tidscan 79 ms ok 142 + tidrangescan 76 ms ok 143 + collate.icu.utf8 605 ms ok 144 + incremental_sort 287 ms ok 145 + create_role 225 ms ok 146 + without_overlaps 340 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 147 + rules 838 ms ok 148 + psql 855 ms ok 149 + psql_crosstab 81 ms ok 150 + amutils 49 ms ok 151 + stats_ext 1785 ms ok 152 + collate.linux.utf8 44 ms ok 153 + collate.windows.win1252 45 ms ok 154 - select_parallel 692 ms ok 155 - write_parallel 165 ms ok 156 - vacuum_parallel 148 ms # parallel group (2 tests): subscription publication ok 157 + publication 1534 ms ok 158 + subscription 182 ms # parallel group (17 tests): portals_p2 advisory_lock functional_deps combocid xmlmap dependency indirect_toast select_views guc tsdicts equivclass bitmapops window tsearch foreign_data cluster foreign_key ok 159 + select_views 263 ms ok 160 + portals_p2 138 ms ok 161 + foreign_key 4397 ms ok 162 + cluster 2658 ms ok 163 + dependency 248 ms ok 164 + guc 599 ms ok 165 + bitmapops 720 ms ok 166 + combocid 208 ms ok 167 + tsearch 1214 ms ok 168 + tsdicts 654 ms ok 169 + foreign_data 1664 ms ok 170 + window 1183 ms ok 171 + xmlmap 216 ms ok 172 + functional_deps 158 ms ok 173 + advisory_lock 130 ms ok 174 + indirect_toast 226 ms ok 175 + equivclass 638 ms # parallel group (7 tests): json_encoding jsonpath_encoding sqljson jsonpath json jsonb_jsonpath jsonb ok 176 + json 446 ms ok 177 + jsonb 914 ms ok 178 + json_encoding 112 ms ok 179 + jsonpath 288 ms ok 180 + jsonpath_encoding 178 ms ok 181 + jsonb_jsonpath 507 ms ok 182 + sqljson 282 ms # parallel group (18 tests): prepare limit returning plancache polymorphism sequence copy2 temp conversion largeobject with rowtypes truncate rangefuncs domain xml plpgsql alter_table ok 183 + plancache 942 ms ok 184 + limit 592 ms ok 185 + plpgsql 2851 ms ok 186 + copy2 1146 ms ok 187 + temp 1164 ms ok 188 + domain 1380 ms ok 189 + rangefuncs 1373 ms ok 190 + prepare 576 ms ok 191 + conversion 1189 ms ok 192 + truncate 1284 ms ok 193 + alter_table 6442 ms ok 194 + sequence 1091 ms ok 195 + polymorphism 931 ms ok 196 + rowtypes 1247 ms ok 197 + returning 854 ms ok 198 + largeobject 1221 ms ok 199 + with 1220 ms ok 200 + xml 2344 ms # parallel group (13 tests): predicate hash_part explain partition_info reloptions memoize partition_aggregate compression tuplesort stats partition_join partition_prune indexing ok 201 + partition_join 3055 ms ok 202 + partition_prune 3583 ms ok 203 + reloptions 568 ms ok 204 + hash_part 375 ms ok 205 + indexing 3867 ms ok 206 + partition_aggregate 1292 ms ok 207 + partition_info 464 ms ok 208 + tuplesort 1786 ms not ok 209 + explain 359 ms ok 210 + compression 1436 ms ok 211 + memoize 880 ms ok 212 + stats 2801 ms ok 213 + predicate 334 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 186 ms ok 215 + event_trigger 507 ms ok 216 - event_trigger_login 271 ms ok 217 - fast_default 3712 ms ok 218 - tablespace 3417 ms 1..218 # 1 of 218 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/explain.out /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/explain.out --- /Users/admin/pgsql/src/test/regress/expected/explain.out 2024-03-02 19:30:19 +++ /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/results/explain.out 2024-03-02 19:32:22 @@ -332,16 +332,16 @@ CONTEXT: PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement -- MEMORY option select explain_filter('explain (memory) select * from int8_tbl i8'); - explain_filter ---------------------------------------------------------- - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) + explain_filter +----------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) Memory: used=N bytes allocated=N bytes (2 rows) select explain_filter('explain (memory, analyze) select * from int8_tbl i8'); - explain_filter ------------------------------------------------------------------------------------------------ - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) (actual time=N.N..N.N rows=N loops=N) + explain_filter +------------------------------------------------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) (actual time=N.N..N.N rows=N loops=N) Memory: used=N bytes allocated=N bytes Planning Time: N.N ms Execution Time: N.N ms @@ -360,6 +360,7 @@ Total Cost: N.N + Plan Rows: N + Plan Width: N + + Plan Calls: N + Planning: + Memory Used: N + Memory Allocated: N + @@ -381,6 +382,7 @@ "Total Cost": N.N, + "Plan Rows": N, + "Plan Width": N, + + "Plan Calls": N, + "Actual Startup Time": N.N, + "Actual Total Time": N.N, + "Actual Rows": N, + @@ -400,9 +402,9 @@ prepare int8_query as select * from int8_tbl i8; select explain_filter('explain (memory) execute int8_query'); - explain_filter ---------------------------------------------------------- - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) + explain_filter +----------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) Memory: used=N bytes allocated=N bytes (2 rows) === EOF === [19:32:36.177](56.984s) not ok 5 - regression tests pass [19:32:36.177](0.000s) # Failed test 'regression tests pass' # at /Users/admin/pgsql/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [19:32:36.177](0.000s) # got: '256' # expected: '0' # Checking port 64269 # Found port 64269 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=64269 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/bsrFPucftd Log file: /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [19:32:36.184](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: 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=64268 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/bsrFPucftd dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TDX8/dump1.sql [19:32:43.095](6.910s) 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/bsrFPucftd -p 64268 -P 64269 --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 [19:32:43.937](0.842s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [19:32:43.937](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/bsrFPucftd -p 64268 -P 64269 --clone --check [19:32:46.877](2.940s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [19:32:46.877](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [19:32:46.877](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 18813 ### 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/bsrFPucftd -p 64268 -P 64269 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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* [19:32:50.851](3.973s) ok 12 - run of pg_upgrade --check for new instance [19:32:50.851](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/bsrFPucftd -p 64268 -P 64269 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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 [19:33:32.923](42.072s) ok 14 - run of pg_upgrade for new instance [19:33:32.923](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 22455 [19:33:33.206](0.283s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=64269 host=/var/folders/n8/pp_chp6x3jlfy1n94r6hdjv40000gn/T/bsrFPucftd dbname='postgres' -f /Users/admin/pgsql/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TDX8/dump2.sql [19:33:44.964](11.758s) ok 17 - dump after running pg_upgrade [19:33:45.259](0.295s) ok 18 - old and new dumps match after pg_upgrade [19:33:45.259](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" [19:33:45.394](0.135s) # Looks like you failed 1 test of 18.