[01:11:00.546](0.020s) # testing using transfer mode --copy # Checking port 56731 # Found port 56731 Name: old_node Data directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata Backup directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/backup Archive directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/archives Connection string: port=56731 host=/tmp/fASrQ6pkW6 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [01:11:00.565](0.019s) # initializing database system by running initdb # Running: initdb -D /tmp/cirrus-ci-build/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 "postgres". 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: C.UTF-8 LC_NUMERIC: C.UTF-8 LC_TIME: C.UTF-8 The default text search configuration will be set to "english". Data page checksums are disabled. creating directory /tmp/cirrus-ci-build/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 ... Etc/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 /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l logfile start # Running: /tmp/cirrus-ci-build/build/src/test/regress/pg_regress --config-auth /tmp/cirrus-ci-build/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 /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /tmp/cirrus-ci-build/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 23946 [01:11:02.421](1.857s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [01:11:02.496](0.074s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [01:11:02.657](0.161s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [01:11:02.816](0.160s) ok 4 - created database with ASCII characters from 91 to 127 [01:11:02.817](0.000s) # running regression tests in old instance # using postmaster on /tmp/fASrQ6pkW6, port 56731 ok 1 - test_setup 407 ms # parallel group (20 tests): oid text pg_lsn int4 char txid money varchar int2 name uuid float4 regproc int8 float8 enum bit boolean rangetypes numeric ok 2 + boolean 361 ms ok 3 + char 111 ms ok 4 + name 158 ms ok 5 + varchar 129 ms ok 6 + text 97 ms ok 7 + int2 132 ms ok 8 + int4 107 ms ok 9 + int8 199 ms ok 10 + oid 87 ms ok 11 + float4 172 ms ok 12 + float8 212 ms ok 13 + bit 325 ms ok 14 + numeric 851 ms ok 15 + txid 111 ms ok 16 + uuid 160 ms ok 17 + enum 283 ms ok 18 + money 117 ms ok 19 + rangetypes 845 ms ok 20 + pg_lsn 102 ms ok 21 + regproc 178 ms # parallel group (20 tests): line lseg path time md5 circle macaddr macaddr8 timetz numerology date inet point strings interval timestamp timestamptz polygon multirangetypes box ok 22 + strings 332 ms ok 23 + md5 89 ms ok 24 + numerology 186 ms ok 25 + point 251 ms ok 26 + lseg 64 ms ok 27 + line 59 ms ok 28 + box 1044 ms ok 29 + path 71 ms ok 30 + polygon 542 ms ok 31 + circle 96 ms ok 32 + date 198 ms ok 33 + time 82 ms ok 34 + timetz 128 ms ok 35 + timestamp 444 ms ok 36 + timestamptz 532 ms ok 37 + interval 381 ms ok 38 + inet 207 ms ok 39 + macaddr 106 ms ok 40 + macaddr8 110 ms ok 41 + multirangetypes 842 ms # parallel group (12 tests): comments unicode xid misc_sanity expressions tstypes mvcc type_sanity geometry horology regex opr_sanity ok 42 + geometry 314 ms ok 43 + horology 438 ms ok 44 + tstypes 201 ms ok 45 + regex 811 ms ok 46 + type_sanity 307 ms ok 47 + opr_sanity 858 ms ok 48 + misc_sanity 118 ms ok 49 + comments 41 ms ok 50 + expressions 196 ms ok 51 + unicode 45 ms ok 52 + xid 108 ms ok 53 + mvcc 208 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 339 ms ok 55 + copyselect 50 ms ok 56 + copydml 93 ms ok 57 + insert 733 ms ok 58 + insert_conflict 411 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 29 ms ok 60 + create_misc 94 ms ok 61 + create_operator 41 ms ok 62 + create_procedure 148 ms ok 63 + create_table 1137 ms ok 64 + create_type 91 ms ok 65 + create_schema 71 ms # parallel group (5 tests): index_including index_including_gist create_view create_index_spgist create_index ok 66 + create_index 1631 ms ok 67 + create_index_spgist 1464 ms ok 68 + create_view 937 ms ok 69 + index_including 472 ms ok 70 + index_including_gist 637 ms # parallel group (16 tests): create_cast errors roleattributes create_aggregate hash_func drop_if_exists typed_table create_function_sql create_am select infinite_recurse vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 142 ms ok 72 + create_function_sql 339 ms ok 73 + create_cast 71 ms ok 74 + constraints 936 ms ok 75 + triggers 3684 ms ok 76 + select 408 ms ok 77 + inherit 2651 ms ok 78 + typed_table 250 ms ok 79 + vacuum 867 ms ok 80 + drop_if_exists 165 ms ok 81 + updatable_views 1633 ms ok 82 + roleattributes 111 ms ok 83 + create_am 387 ms ok 84 + hash_func 149 ms ok 85 + errors 77 ms ok 86 + infinite_recurse 793 ms ok 87 - sanity_check 88 ms # parallel group (20 tests): select_distinct_on select_having delete select_implicit case namespace select_into prepared_xacts random transactions portals union select_distinct arrays subselect hash_index update join aggregates btree_index ok 88 + select_into 209 ms ok 89 + select_distinct 620 ms ok 90 + select_distinct_on 82 ms ok 91 + select_implicit 138 ms ok 92 + select_having 82 ms ok 93 + subselect 676 ms ok 94 + union 604 ms ok 95 + case 142 ms ok 96 + join 2078 ms ok 97 + aggregates 2257 ms ok 98 + transactions 351 ms ok 99 + random 254 ms ok 100 + portals 412 ms ok 101 + arrays 659 ms ok 102 + btree_index 3854 ms ok 103 + hash_index 992 ms ok 104 + update 1177 ms ok 105 + delete 94 ms ok 106 + namespace 184 ms ok 107 + prepared_xacts 207 ms # parallel group (20 tests): drop_operator security_label init_privs password lock tablesample object_address replica_identity collate matview identity groupingsets generated rowsecurity spgist gist gin brin join_hash privileges ok 108 + brin 5929 ms ok 109 + gin 2515 ms ok 110 + gist 2385 ms ok 111 + spgist 2087 ms ok 112 + privileges 6533 ms ok 113 + init_privs 126 ms ok 114 + security_label 125 ms ok 115 + collate 903 ms ok 116 + matview 1256 ms ok 117 + lock 261 ms ok 118 + replica_identity 776 ms ok 119 + rowsecurity 2063 ms ok 120 + object_address 312 ms ok 121 + tablesample 266 ms ok 122 + groupingsets 1731 ms ok 123 + drop_operator 88 ms ok 124 + password 255 ms ok 125 + identity 1341 ms ok 126 + generated 2041 ms ok 127 + join_hash 5951 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 300 ms ok 129 + brin_multi 806 ms # parallel group (18 tests): async dbsize collate.utf8 tsrf tid alter_operator create_role tidscan sysviews tidrangescan misc_functions alter_generic incremental_sort misc merge create_table_like collate.icu.utf8 without_overlaps ok 130 + create_table_like 1057 ms ok 131 + alter_generic 393 ms ok 132 + alter_operator 207 ms ok 133 + misc 987 ms ok 134 + async 48 ms ok 135 + dbsize 68 ms ok 136 + merge 1052 ms ok 137 + misc_functions 349 ms not ok 138 + sysviews 311 ms ok 139 + tsrf 135 ms ok 140 + tid 158 ms ok 141 + tidscan 241 ms ok 142 + tidrangescan 327 ms ok 143 + collate.utf8 99 ms ok 144 + collate.icu.utf8 1096 ms ok 145 + incremental_sort 879 ms ok 146 + create_role 231 ms ok 147 + without_overlaps 1323 ms # parallel group (7 tests): collate.linux.utf8 amutils collate.windows.win1252 psql_crosstab rules psql stats_ext ok 148 + rules 849 ms ok 149 + psql 926 ms ok 150 + psql_crosstab 77 ms ok 151 + amutils 32 ms ok 152 + stats_ext 2113 ms ok 153 + collate.linux.utf8 30 ms ok 154 + collate.windows.win1252 33 ms ok 155 - select_parallel 7191 ms ok 156 - write_parallel 190 ms ok 157 - vacuum_parallel 244 ms # parallel group (2 tests): subscription publication ok 158 + publication 1953 ms ok 159 + subscription 113 ms # parallel group (17 tests): combocid portals_p2 xmlmap advisory_lock tsdicts equivclass functional_deps guc dependency select_views bitmapops window cluster indirect_toast foreign_data tsearch foreign_key ok 160 + select_views 921 ms ok 161 + portals_p2 116 ms ok 162 + foreign_key 4273 ms ok 163 + cluster 1775 ms ok 164 + dependency 437 ms ok 165 + guc 414 ms ok 166 + bitmapops 1638 ms ok 167 + combocid 103 ms ok 168 + tsearch 3286 ms ok 169 + tsdicts 255 ms ok 170 + foreign_data 3180 ms ok 171 + window 1731 ms ok 172 + xmlmap 124 ms ok 173 + functional_deps 263 ms ok 174 + advisory_lock 135 ms ok 175 + indirect_toast 1979 ms ok 176 + equivclass 255 ms # parallel group (8 tests): jsonpath_encoding json_encoding jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 224 ms ok 178 + jsonb 641 ms ok 179 + json_encoding 43 ms ok 180 + jsonpath 94 ms ok 181 + jsonpath_encoding 34 ms ok 182 + jsonb_jsonpath 255 ms ok 183 + sqljson 107 ms ok 184 + sqljson_queryfuncs 168 ms # parallel group (18 tests): prepare returning plancache limit conversion temp copy2 sequence polymorphism truncate rowtypes largeobject with domain rangefuncs xml plpgsql alter_table ok 185 + plancache 320 ms ok 186 + limit 373 ms ok 187 + plpgsql 5082 ms ok 188 + copy2 582 ms ok 189 + temp 469 ms ok 190 + domain 1459 ms ok 191 + rangefuncs 1610 ms ok 192 + prepare 180 ms ok 193 + conversion 407 ms ok 194 + truncate 715 ms ok 195 + alter_table 5587 ms ok 196 + sequence 606 ms ok 197 + polymorphism 685 ms ok 198 + rowtypes 929 ms ok 199 + returning 271 ms ok 200 + largeobject 1032 ms ok 201 + with 1410 ms ok 202 + xml 3084 ms # parallel group (13 tests): hash_part explain reloptions partition_info predicate compression memoize stats partition_aggregate tuplesort partition_join indexing partition_prune ok 203 + partition_join 4292 ms ok 204 + partition_prune 5120 ms ok 205 + reloptions 191 ms ok 206 + hash_part 139 ms ok 207 + indexing 4622 ms ok 208 + partition_aggregate 3199 ms ok 209 + partition_info 250 ms ok 210 + tuplesort 3606 ms ok 211 + explain 181 ms ok 212 + compression 621 ms ok 213 + memoize 980 ms ok 214 + stats 2080 ms ok 215 + predicate 254 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 695 ms ok 217 + event_trigger 762 ms ok 218 - event_trigger_login 89 ms ok 219 - fast_default 355 ms ok 220 - tablespace 680 ms 1..220 # 1 of 220 tests failed. # The differences that caused some tests to fail can be viewed in the file "/tmp/cirrus-ci-build/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 "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out --- /tmp/cirrus-ci-build/src/test/regress/expected/sysviews.out 2024-03-29 01:07:47.770799166 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/sysviews.out 2024-03-29 01:11:25.802661505 +0000 @@ -134,7 +134,8 @@ enable_seqscan | on enable_sort | on enable_tidscan | on -(23 rows) + enable_toast_cache | off +(24 rows) -- There are always wait event descriptions for various types. select type, count(*) > 0 as ok FROM pg_wait_events === EOF === [01:11:56.865](54.048s) not ok 5 - regression tests pass [01:11:56.865](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [01:11:56.865](0.000s) # got: '256' # expected: '0' # Checking port 56732 # Found port 56732 Name: new_node Data directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata Backup directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/backup Archive directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/archives Connection string: port=56732 host=/tmp/fASrQ6pkW6 Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [01:11:56.874](0.009s) # initializing database system by running initdb # Running: initdb -D /tmp/cirrus-ci-build/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 "postgres". This user must also own the server process. The database cluster will be initialized with this locale configuration: locale provider: libc LC_COLLATE: C.UTF-8 LC_CTYPE: C.UTF-8 LC_MESSAGES: C LC_MONETARY: C.UTF-8 LC_NUMERIC: C.UTF-8 LC_TIME: C.UTF-8 The default text search configuration will be set to "english". Data page checksums are disabled. creating directory /tmp/cirrus-ci-build/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 ... Etc/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 /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l logfile start # Running: /tmp/cirrus-ci-build/build/src/test/regress/pg_regress --config-auth /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata # Running: pg_dumpall --no-sync -d port=56731 host=/tmp/fASrQ6pkW6 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_PuAy/dump1.sql [01:12:01.328](4.454s) ok 6 - dump before running pg_upgrade ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /tmp/cirrus-ci-build/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 /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/does/not/exist/ -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/fASrQ6pkW6 -p 56731 -P 56732 --copy --check check for "/tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/does/not/exist" failed: No such file or directory Failure, exiting [01:12:01.582](0.254s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [01:12:01.583](0.000s) ok 8 - pg_upgrade_output.d/ not removed after pg_upgrade failure # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/fASrQ6pkW6 -p 56731 -P 56732 --copy --check [01:12:02.634](1.051s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [01:12:02.634](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [01:12:02.634](0.000s) ok 11 - invalid database causes failure stderr /(?^:^$)/ ### Starting node "old_node" # Running: pg_ctl -w -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -l /tmp/cirrus-ci-build/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 36925 ### Stopping node "old_node" using mode fast # Running: pg_ctl -D /tmp/cirrus-ci-build/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 /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/fASrQ6pkW6 -p 56731 -P 56732 --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* [01:12:05.012](2.378s) ok 12 - run of pg_upgrade --check for new instance [01:12:05.012](0.000s) ok 13 - pg_upgrade_output.d/ removed after pg_upgrade --check success # Running: pg_upgrade --no-sync -d /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -b /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -B /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin -s /tmp/fASrQ6pkW6 -p 56731 -P 56732 --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: /tmp/cirrus-ci-build/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 [01:12:19.687](14.675s) ok 14 - run of pg_upgrade for new instance [01:12:19.687](0.000s) ok 15 - pg_upgrade_output.d/ removed after pg_upgrade success ### Starting node "new_node" # Running: pg_ctl -w -D /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_new_node_data/pgdata -l /tmp/cirrus-ci-build/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 40146 [01:12:19.892](0.205s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=56732 host=/tmp/fASrQ6pkW6 dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_PuAy/dump2.sql [01:12:23.549](3.656s) ok 17 - dump after running pg_upgrade [01:12:23.632](0.084s) ok 18 - old and new dumps match after pg_upgrade [01:12:23.633](0.000s) 1..18 ### Stopping node "new_node" using mode immediate # Running: pg_ctl -D /tmp/cirrus-ci-build/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" [01:12:23.744](0.111s) # Looks like you failed 1 test of 18.