[04:37:16.729](0.068s) # testing using transfer mode --copy # Checking port 58985 # Found port 58985 Name: old_node Data directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata Backup directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/backup Archive directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/archives Connection string: port=58985 host=C:/Windows/TEMP/5dVERCG0Or Log file: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\log/002_pg_upgrade_old_node.log [04:37:16.771](0.042s) # initializing database system by running initdb # Running: initdb -D C:\cirrus\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 "SYSTEM". 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: English_United States.1252 LC_MONETARY: English_United States.1252 LC_NUMERIC: English_United States.1252 LC_TIME: English_United States.1252 The default text search configuration will be set to "english". Data page checksums are disabled. creating directory C:/cirrus/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 ... windows selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Atlantic/Reykjavik 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 ^"C^:^\cirrus^\build^/testrun^/pg^_upgrade^/002^_pg^_upgrade^\data^/t^_002^_pg^_upgrade^_old^_node^_data^/pgdata^" -l logfile start # Running: C:\cirrus\build\src/test\regress\pg_regress.exe --config-auth C:\cirrus\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 C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -l C:\cirrus\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 620 [04:37:22.605](5.834s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [04:37:23.001](0.396s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [04:37:23.399](0.397s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [04:37:24.031](0.632s) ok 4 - created database with ASCII characters from 91 to 127 [04:37:24.034](0.003s) # running regression tests in old instance # using postmaster on C:/Windows/TEMP/5dVERCG0Or, port 58985 ok 1 - test_setup 605 ms # parallel group (20 tests): oid name varchar float4 uuid pg_lsn text int4 money txid regproc int2 bit int8 float8 boolean enum char rangetypes numeric ok 2 + boolean 822 ms ok 3 + char 928 ms ok 4 + name 669 ms ok 5 + varchar 667 ms ok 6 + text 744 ms ok 7 + int2 792 ms ok 8 + int4 741 ms ok 9 + int8 789 ms ok 10 + oid 590 ms ok 11 + float4 653 ms ok 12 + float8 798 ms ok 13 + bit 777 ms ok 14 + numeric 1508 ms ok 15 + txid 732 ms ok 16 + uuid 723 ms ok 17 + enum 790 ms ok 18 + money 720 ms ok 19 + rangetypes 1368 ms ok 20 + pg_lsn 716 ms ok 21 + regproc 764 ms # parallel group (20 tests): circle path md5 macaddr point lseg time date timetz strings macaddr8 inet polygon numerology line interval timestamp timestamptz multirangetypes box ok 22 + strings 874 ms ok 23 + md5 785 ms ok 24 + numerology 949 ms ok 25 + point 782 ms ok 26 + lseg 780 ms ok 27 + line 1269 ms ok 28 + box 1377 ms ok 29 + path 775 ms ok 30 + polygon 939 ms ok 31 + circle 665 ms ok 32 + date 803 ms ok 33 + time 768 ms ok 34 + timetz 800 ms ok 35 + timestamp 1268 ms ok 36 + timestamptz 1309 ms ok 37 + interval 1252 ms ok 38 + inet 876 ms ok 39 + macaddr 758 ms ok 40 + macaddr8 873 ms ok 41 + multirangetypes 1355 ms # parallel group (12 tests): misc_sanity mvcc type_sanity xid geometry comments unicode expressions tstypes horology regex opr_sanity ok 42 + geometry 597 ms ok 43 + horology 934 ms ok 44 + tstypes 629 ms ok 45 + regex 1255 ms ok 46 + type_sanity 463 ms ok 47 + opr_sanity 1254 ms ok 48 + misc_sanity 343 ms ok 49 + comments 585 ms ok 50 + expressions 619 ms ok 51 + unicode 582 ms ok 52 + xid 580 ms ok 53 + mvcc 334 ms # parallel group (5 tests): copydml copyselect copy insert insert_conflict ok 54 + copy 1922 ms ok 55 + copyselect 1647 ms ok 56 + copydml 1268 ms ok 57 + insert 2555 ms ok 58 + insert_conflict 2871 ms # parallel group (7 tests): create_misc create_operator create_procedure create_function_c create_type create_schema create_table ok 59 + create_function_c 345 ms ok 60 + create_misc 322 ms ok 61 + create_operator 321 ms ok 62 + create_procedure 319 ms ok 63 + create_table 952 ms ok 64 + create_type 338 ms ok 65 + create_schema 361 ms # parallel group (5 tests): index_including create_index_spgist create_view index_including_gist create_index ok 66 + create_index 3305 ms ok 67 + create_index_spgist 1051 ms ok 68 + create_view 1050 ms ok 69 + index_including 1000 ms ok 70 + index_including_gist 1379 ms # parallel group (16 tests): roleattributes create_aggregate hash_func select drop_if_exists create_am create_cast typed_table infinite_recurse errors create_function_sql updatable_views constraints vacuum inherit triggers ok 71 + create_aggregate 886 ms ok 72 + create_function_sql 1932 ms ok 73 + create_cast 1604 ms ok 74 + constraints 2344 ms ok 75 + triggers 4726 ms ok 76 + select 896 ms ok 77 + inherit 2736 ms ok 78 + typed_table 1596 ms ok 79 + vacuum 2336 ms ok 80 + drop_if_exists 1017 ms ok 81 + updatable_views 2155 ms ok 82 + roleattributes 686 ms ok 83 + create_am 1012 ms ok 84 + hash_func 883 ms ok 85 + errors 1752 ms ok 86 + infinite_recurse 1750 ms ok 87 - sanity_check 441 ms # parallel group (20 tests): select_distinct_on select_into select_having namespace select_implicit case union update portals delete transactions subselect prepared_xacts random arrays select_distinct join hash_index aggregates btree_index ok 88 + select_into 1571 ms ok 89 + select_distinct 2216 ms ok 90 + select_distinct_on 1331 ms ok 91 + select_implicit 1602 ms ok 92 + select_having 1600 ms ok 93 + subselect 1659 ms ok 94 + union 1657 ms ok 95 + case 1652 ms ok 96 + join 2765 ms ok 97 + aggregates 3524 ms ok 98 + transactions 1651 ms ok 99 + random 1684 ms ok 100 + portals 1648 ms ok 101 + arrays 2128 ms ok 102 + btree_index 6236 ms ok 103 + hash_index 2826 ms ok 104 + update 1641 ms ok 105 + delete 1639 ms ok 106 + namespace 1578 ms ok 107 + prepared_xacts 1670 ms # parallel group (20 tests): drop_operator password init_privs security_label object_address spgist lock matview tablesample replica_identity collate groupingsets identity gin generated rowsecurity gist join_hash brin privileges ok 108 + brin 10393 ms ok 109 + gin 3269 ms ok 110 + gist 4097 ms ok 111 + spgist 2956 ms ok 112 + privileges 11680 ms ok 113 + init_privs 2553 ms ok 114 + security_label 2551 ms ok 115 + collate 3162 ms ok 116 + matview 3065 ms ok 117 + lock 2945 ms ok 118 + replica_identity 3087 ms not ok 119 + rowsecurity 3456 ms ok 120 + object_address 2936 ms ok 121 + tablesample 3082 ms ok 122 + groupingsets 3147 ms ok 123 + drop_operator 1922 ms ok 124 + password 2529 ms ok 125 + identity 3236 ms ok 126 + generated 3234 ms ok 127 + join_hash 10300 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 939 ms ok 129 + brin_multi 1936 ms # parallel group (18 tests): tidscan alter_generic tid tidrangescan create_role collate.utf8 collate.icu.utf8 async misc alter_operator sysviews tsrf incremental_sort dbsize misc_functions create_table_like without_overlaps merge ok 130 + create_table_like 1746 ms ok 131 + alter_generic 1040 ms ok 132 + alter_operator 1465 ms ok 133 + misc 1463 ms ok 134 + async 1404 ms ok 135 + dbsize 1518 ms ok 136 + merge 1877 ms ok 137 + misc_functions 1711 ms ok 138 + sysviews 1453 ms ok 139 + tsrf 1451 ms ok 140 + tid 1023 ms ok 141 + tidscan 1019 ms ok 142 + tidrangescan 1019 ms ok 143 + collate.utf8 1167 ms ok 144 + collate.icu.utf8 1165 ms ok 145 + incremental_sort 1499 ms ok 146 + create_role 1114 ms ok 147 + without_overlaps 1855 ms # parallel group (7 tests): psql_crosstab collate.windows.win1252 amutils collate.linux.utf8 psql rules stats_ext ok 148 + rules 1350 ms ok 149 + psql 1326 ms ok 150 + psql_crosstab 443 ms ok 151 + amutils 442 ms ok 152 + stats_ext 2850 ms ok 153 + collate.linux.utf8 530 ms ok 154 + collate.windows.win1252 436 ms ok 155 - select_parallel 9595 ms ok 156 - write_parallel 897 ms ok 157 - vacuum_parallel 494 ms # parallel group (2 tests): subscription publication ok 158 + publication 991 ms ok 159 + subscription 343 ms # parallel group (17 tests): advisory_lock xmlmap portals_p2 equivclass dependency select_views functional_deps window guc combocid tsearch cluster tsdicts indirect_toast foreign_data bitmapops foreign_key ok 160 + select_views 2242 ms ok 161 + portals_p2 1031 ms ok 162 + foreign_key 4681 ms ok 163 + cluster 2681 ms ok 164 + dependency 2118 ms ok 165 + guc 2553 ms ok 166 + bitmapops 2853 ms ok 167 + combocid 2625 ms ok 168 + tsearch 2673 ms ok 169 + tsdicts 2725 ms ok 170 + foreign_data 2787 ms ok 171 + window 2442 ms ok 172 + xmlmap 781 ms ok 173 + functional_deps 2220 ms ok 174 + advisory_lock 777 ms ok 175 + indirect_toast 2764 ms ok 176 + equivclass 1279 ms # parallel group (9 tests): sqljson_jsontable jsonpath_encoding json_encoding sqljson jsonpath json sqljson_queryfuncs jsonb_jsonpath jsonb ok 177 + json 531 ms ok 178 + jsonb 911 ms ok 179 + json_encoding 396 ms ok 180 + jsonpath 466 ms ok 181 + jsonpath_encoding 346 ms ok 182 + jsonb_jsonpath 705 ms ok 183 + sqljson 433 ms ok 184 + sqljson_queryfuncs 697 ms ok 185 + sqljson_jsontable 339 ms # parallel group (18 tests): prepare conversion plancache returning truncate polymorphism xml rangefuncs rowtypes copy2 largeobject sequence temp with limit domain plpgsql alter_table ok 186 + plancache 1418 ms ok 187 + limit 3441 ms ok 188 + plpgsql 4520 ms ok 189 + copy2 2901 ms ok 190 + temp 3173 ms ok 191 + domain 4077 ms ok 192 + rangefuncs 2624 ms ok 193 + prepare 887 ms ok 194 + conversion 1206 ms ok 195 + truncate 1583 ms ok 196 + alter_table 5422 ms ok 197 + sequence 2889 ms ok 198 + polymorphism 2127 ms ok 199 + rowtypes 2834 ms ok 200 + returning 1397 ms ok 201 + largeobject 2882 ms ok 202 + with 3418 ms ok 203 + xml 2117 ms # parallel group (13 tests): reloptions predicate compression partition_info memoize partition_join explain hash_part indexing stats tuplesort partition_aggregate partition_prune ok 204 + partition_join 2563 ms ok 205 + partition_prune 5723 ms ok 206 + reloptions 1151 ms ok 207 + hash_part 2656 ms ok 208 + indexing 2861 ms ok 209 + partition_aggregate 4039 ms ok 210 + partition_info 1953 ms ok 211 + tuplesort 3528 ms ok 212 + explain 2550 ms ok 213 + compression 1434 ms ok 214 + memoize 1950 ms ok 215 + stats 3502 ms ok 216 + predicate 1257 ms # parallel group (2 tests): oidjoins event_trigger ok 217 + oidjoins 567 ms ok 218 + event_trigger 761 ms ok 219 - event_trigger_login 396 ms ok 220 - fast_default 750 ms ok 221 - tablespace 1207 ms 1..221 # 1 of 221 tests failed. # The differences that caused some tests to fail can be viewed in the file "C:/cirrus/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 "C:/cirrus/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/regression.diffs === diff -w -U3 C:/cirrus/src/test/regress/expected/rowsecurity.out C:/cirrus/build/testrun/pg_upgrade/002_pg_upgrade/data/results/rowsecurity.out --- C:/cirrus/src/test/regress/expected/rowsecurity.out 2024-04-05 04:35:18.292619900 +0000 +++ C:/cirrus/build/testrun/pg_upgrade/002_pg_upgrade/data/results/rowsecurity.out 2024-04-05 04:38:11.838554500 +0000 @@ -144,8 +144,7 @@ | | | | | | FROM uaccount +| | | | | | | WHERE (uaccount.pguser = CURRENT_USER))) | regress_rls_schema | document | p1r | RESTRICTIVE | {regress_rls_dave} | ALL | (cid <> 44) | - regress_rls_schema | document | p2r | RESTRICTIVE | {regress_rls_dave} | ALL | ((cid <> 44) AND (cid < 50)) | -(3 rows) +(2 rows) -- viewpoint from regress_rls_bob SET SESSION AUTHORIZATION regress_rls_bob; === EOF === [04:39:17.711](113.677s) not ok 5 - regression tests pass [04:39:17.717](0.007s) # Failed test 'regression tests pass' # at C:/cirrus/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [04:39:17.717](0.000s) # got: '256' # expected: '0' # Checking port 58986 # Found port 58986 Name: new_node Data directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata Backup directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/backup Archive directory: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/archives Connection string: port=58986 host=C:/Windows/TEMP/5dVERCG0Or Log file: C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\log/002_pg_upgrade_new_node.log [04:39:17.765](0.047s) # initializing database system by running initdb # Running: initdb -D C:\cirrus\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 "SYSTEM". This user must also own the server process. The database cluster will be initialized with locale "English_United States.1252". The default text search configuration will be set to "english". Data page checksums are disabled. creating directory C:/cirrus/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 ... windows selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Atlantic/Reykjavik 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 ^"C^:^\cirrus^\build^/testrun^/pg^_upgrade^/002^_pg^_upgrade^\data^/t^_002^_pg^_upgrade^_new^_node^_data^/pgdata^" -l logfile start # Running: C:\cirrus\build\src/test\regress\pg_regress.exe --config-auth C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata # Running: pg_dumpall --no-sync -d port=58985 host=C:/Windows/TEMP/5dVERCG0Or dbname='postgres' -f C:\cirrus\build\testrun\pg_upgrade\002_pg_upgrade\data\tmp_test_q3Xm/dump1.sql [04:39:26.915](9.150s) ok 6 - dump before running pg_upgrade ### Stopping node "old_node" using mode fast # Running: pg_ctl -D C:\cirrus\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 C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata -b C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin/does/not/exist/ -B C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -s C:/Windows/TEMP/5dVERCG0Or -p 58985 -P 58986 --copy --check check for "C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin/does/not/exist" failed: No such file or directory Failure, exiting [04:39:28.196](1.282s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [04:39:28.197](0.001s) ok 8 - pg_upgrade_output.d/ not removed after pg_upgrade failure # Running: pg_upgrade --no-sync -d C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata -b C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -B C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -s C:/Windows/TEMP/5dVERCG0Or -p 58985 -P 58986 --copy --check [04:39:32.185](3.987s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [04:39:32.185](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [04:39:32.186](0.000s) ok 11 - invalid database causes failure stderr /(?^:^$)/ ### Starting node "old_node" # Running: pg_ctl -w -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -l C:\cirrus\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 4436 ### Stopping node "old_node" using mode fast # Running: pg_ctl -D C:\cirrus\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 C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata -b C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -B C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -s C:/Windows/TEMP/5dVERCG0Or -p 58985 -P 58986 --copy --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* [04:39:39.881](7.695s) ok 12 - run of pg_upgrade --check for new instance [04:39:39.882](0.001s) ok 13 - pg_upgrade_output.d/ removed after pg_upgrade --check success # Running: pg_upgrade --no-sync -d C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_old_node_data/pgdata -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata -b C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -B C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin -s C:/Windows/TEMP/5dVERCG0Or -p 58985 -P 58986 --copy 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 Copying 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: C:/cirrus/build/TMP_IN~1/usr/local/pgsql/bin/vacuumdb --all --analyze-in-stages Running this script will delete the old cluster's data files: delete_old_cluster.bat [04:40:24.403](44.521s) ok 14 - run of pg_upgrade for new instance [04:40:24.403](0.000s) ok 15 - pg_upgrade_output.d/ removed after pg_upgrade success ### Starting node "new_node" # Running: pg_ctl -w -D C:\cirrus\build/testrun/pg_upgrade/002_pg_upgrade\data/t_002_pg_upgrade_new_node_data/pgdata -l C:\cirrus\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 4800 [04:40:25.075](0.673s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=58986 host=C:/Windows/TEMP/5dVERCG0Or dbname='postgres' -f C:\cirrus\build\testrun\pg_upgrade\002_pg_upgrade\data\tmp_test_q3Xm/dump2.sql [04:40:33.691](8.615s) ok 17 - dump after running pg_upgrade [04:40:34.130](0.440s) ok 18 - old and new dumps match after pg_upgrade [04:40:34.153](0.023s) 1..18 ### Stopping node "new_node" using mode immediate # Running: pg_ctl -D C:\cirrus\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" [04:40:34.756](0.603s) # Looks like you failed 1 test of 18.