[05:18:31.988](0.017s) # testing using transfer mode --link # Checking port 57897 # Found port 57897 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=57897 host=/tmp/pEtZgWYjvr Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [05:18:31.995](0.007s) # 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: 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 /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 ... 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 6109 [05:18:34.106](2.111s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [05:18:34.190](0.084s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [05:18:34.256](0.066s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [05:18:34.310](0.055s) ok 4 - created database with ASCII characters from 91 to 127 [05:18:34.312](0.001s) # running regression tests in old instance # using postmaster on /tmp/pEtZgWYjvr, port 57897 ok 1 - test_setup 320 ms # parallel group (20 tests): varchar pg_lsn char oid uuid name txid text int2 int4 float4 regproc boolean money bit enum float8 int8 rangetypes numeric ok 2 + boolean 258 ms ok 3 + char 118 ms ok 4 + name 164 ms ok 5 + varchar 108 ms ok 6 + text 188 ms ok 7 + int2 208 ms ok 8 + int4 222 ms ok 9 + int8 363 ms ok 10 + oid 126 ms ok 11 + float4 227 ms ok 12 + float8 344 ms ok 13 + bit 322 ms ok 14 + numeric 1130 ms ok 15 + txid 170 ms ok 16 + uuid 158 ms ok 17 + enum 340 ms ok 18 + money 261 ms ok 19 + rangetypes 752 ms ok 20 + pg_lsn 115 ms ok 21 + regproc 240 ms # parallel group (20 tests): md5 lseg path circle time line timetz macaddr point numerology macaddr8 date polygon inet box timestamp interval strings timestamptz multirangetypes ok 22 + strings 581 ms ok 23 + md5 58 ms ok 24 + numerology 201 ms ok 25 + point 153 ms ok 26 + lseg 64 ms ok 27 + line 111 ms ok 28 + box 360 ms ok 29 + path 77 ms ok 30 + polygon 268 ms ok 31 + circle 84 ms ok 32 + date 245 ms ok 33 + time 103 ms ok 34 + timetz 110 ms ok 35 + timestamp 450 ms ok 36 + timestamptz 599 ms ok 37 + interval 459 ms ok 38 + inet 299 ms ok 39 + macaddr 130 ms ok 40 + macaddr8 218 ms ok 41 + multirangetypes 661 ms # parallel group (12 tests): comments misc_sanity mvcc unicode xid type_sanity expressions tstypes horology geometry regex opr_sanity ok 42 + geometry 346 ms ok 43 + horology 300 ms ok 44 + tstypes 258 ms ok 45 + regex 363 ms ok 46 + type_sanity 177 ms ok 47 + opr_sanity 486 ms ok 48 + misc_sanity 43 ms ok 49 + comments 24 ms ok 50 + expressions 224 ms ok 51 + unicode 84 ms ok 52 + xid 140 ms ok 53 + mvcc 79 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 336 ms ok 55 + copyselect 88 ms ok 56 + copydml 116 ms ok 57 + insert 1127 ms ok 58 + insert_conflict 724 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_procedure create_misc create_table ok 59 + create_function_c 37 ms ok 60 + create_misc 153 ms ok 61 + create_operator 112 ms ok 62 + create_procedure 143 ms ok 63 + create_table 1900 ms ok 64 + create_type 143 ms ok 65 + create_schema 112 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1848 ms ok 67 + create_index_spgist 829 ms ok 68 + create_view 1172 ms ok 69 + index_including 532 ms ok 70 + index_including_gist 514 ms # parallel group (16 tests): create_cast hash_func roleattributes create_aggregate select errors typed_table drop_if_exists infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 289 ms ok 72 + create_function_sql 527 ms ok 73 + create_cast 137 ms ok 74 + constraints 1979 ms ok 75 + triggers 5674 ms ok 76 + select 306 ms ok 77 + inherit 3936 ms ok 78 + typed_table 337 ms ok 79 + vacuum 854 ms ok 80 + drop_if_exists 397 ms ok 81 + updatable_views 3474 ms ok 82 + roleattributes 212 ms ok 83 + create_am 588 ms ok 84 + hash_func 175 ms ok 85 + errors 335 ms ok 86 + infinite_recurse 429 ms ok 87 - sanity_check 157 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit random namespace case select_into prepared_xacts select_distinct subselect transactions portals union arrays hash_index update aggregates btree_index join ok 88 + select_into 298 ms ok 89 + select_distinct 381 ms ok 90 + select_distinct_on 93 ms ok 91 + select_implicit 163 ms ok 92 + select_having 153 ms ok 93 + subselect 738 ms ok 94 + union 806 ms ok 95 + case 279 ms ok 96 + join 2064 ms ok 97 + aggregates 1750 ms ok 98 + transactions 771 ms ok 99 + random 219 ms ok 100 + portals 801 ms ok 101 + arrays 1112 ms ok 102 + btree_index 1970 ms ok 103 + hash_index 1135 ms ok 104 + update 1547 ms ok 105 + delete 103 ms ok 106 + namespace 224 ms ok 107 + prepared_xacts 350 ms # parallel group (20 tests): init_privs drop_operator tablesample password security_label lock object_address groupingsets spgist replica_identity collate gin gist brin matview identity privileges join_hash generated rowsecurity ok 108 + brin 1740 ms ok 109 + gin 1638 ms ok 110 + gist 1711 ms ok 111 + spgist 1123 ms ok 112 + privileges 3274 ms ok 113 + init_privs 100 ms ok 114 + security_label 460 ms ok 115 + collate 1175 ms ok 116 + matview 1975 ms ok 117 + lock 879 ms ok 118 + replica_identity 1132 ms ok 119 + rowsecurity 4521 ms ok 120 + object_address 997 ms ok 121 + tablesample 318 ms ok 122 + groupingsets 1048 ms ok 123 + drop_operator 157 ms ok 124 + password 401 ms ok 125 + identity 2050 ms ok 126 + generated 4042 ms ok 127 + join_hash 3980 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 226 ms ok 129 + brin_multi 898 ms # parallel group (18 tests): async dbsize collate.utf8 tidscan sysviews tid tidrangescan tsrf misc alter_operator misc_functions incremental_sort create_role alter_generic create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 886 ms ok 131 + alter_generic 564 ms ok 132 + alter_operator 360 ms ok 133 + misc 269 ms ok 134 + async 59 ms ok 135 + dbsize 94 ms ok 136 + merge 994 ms ok 137 + misc_functions 374 ms ok 138 + sysviews 197 ms ok 139 + tsrf 266 ms ok 140 + tid 233 ms ok 141 + tidscan 186 ms ok 142 + tidrangescan 234 ms ok 143 + collate.utf8 148 ms ok 144 + collate.icu.utf8 965 ms ok 145 + incremental_sort 434 ms ok 146 + create_role 437 ms ok 147 + without_overlaps 1360 ms # parallel group (7 tests): collate.linux.utf8 amutils collate.windows.win1252 psql_crosstab psql rules stats_ext ok 148 + rules 1594 ms ok 149 + psql 1286 ms ok 150 + psql_crosstab 75 ms ok 151 + amutils 31 ms ok 152 + stats_ext 2948 ms ok 153 + collate.linux.utf8 14 ms ok 154 + collate.windows.win1252 31 ms ok 155 - select_parallel 1624 ms ok 156 - write_parallel 155 ms ok 157 - vacuum_parallel 104 ms # parallel group (2 tests): subscription publication ok 158 + publication 2052 ms ok 159 + subscription 105 ms # parallel group (17 tests): xmlmap portals_p2 advisory_lock functional_deps combocid bitmapops indirect_toast select_views dependency tsdicts equivclass guc tsearch window cluster foreign_data foreign_key ok 160 + select_views 594 ms ok 161 + portals_p2 277 ms ok 162 + foreign_key 6572 ms ok 163 + cluster 1253 ms ok 164 + dependency 640 ms ok 165 + guc 717 ms ok 166 + bitmapops 567 ms ok 167 + combocid 410 ms ok 168 + tsearch 1188 ms ok 169 + tsdicts 655 ms ok 170 + foreign_data 2814 ms ok 171 + window 1196 ms ok 172 + xmlmap 258 ms ok 173 + functional_deps 403 ms ok 174 + advisory_lock 332 ms ok 175 + indirect_toast 582 ms ok 176 + equivclass 690 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable sqljson jsonpath sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 669 ms ok 178 + jsonb 1132 ms ok 179 + json_encoding 151 ms ok 180 + jsonpath 387 ms ok 181 + jsonpath_encoding 124 ms ok 182 + jsonb_jsonpath 835 ms ok 183 + sqljson 363 ms ok 184 + sqljson_queryfuncs 594 ms ok 185 + sqljson_jsontable 288 ms # parallel group (18 tests): prepare conversion returning limit plancache temp rowtypes sequence polymorphism truncate copy2 largeobject with xml rangefuncs domain plpgsql alter_table ok 186 + plancache 606 ms ok 187 + limit 469 ms ok 188 + plpgsql 3273 ms ok 189 + copy2 1256 ms ok 190 + temp 732 ms ok 191 + domain 1727 ms ok 192 + rangefuncs 1501 ms ok 193 + prepare 146 ms ok 194 + conversion 393 ms ok 195 + truncate 1173 ms not ok 196 + alter_table 8121 ms ok 197 + sequence 1011 ms ok 198 + polymorphism 1165 ms ok 199 + rowtypes 971 ms ok 200 + returning 441 ms ok 201 + largeobject 1288 ms ok 202 + with 1329 ms ok 203 + xml 1500 ms # parallel group (15 tests): predicate hash_part explain reloptions partition_info memoize compression partition_aggregate stats tuplesort partition_merge partition_join partition_split partition_prune indexing ok 204 + partition_merge 4048 ms ok 205 + partition_split 4577 ms ok 206 + partition_join 4113 ms ok 207 + partition_prune 5766 ms ok 208 + reloptions 669 ms ok 209 + hash_part 339 ms ok 210 + indexing 6445 ms ok 211 + partition_aggregate 2297 ms ok 212 + partition_info 703 ms ok 213 + tuplesort 3658 ms ok 214 + explain 566 ms ok 215 + compression 1849 ms ok 216 + memoize 802 ms ok 217 + stats 3271 ms ok 218 + predicate 278 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 467 ms ok 220 + event_trigger 512 ms ok 221 - event_trigger_login 63 ms ok 222 - fast_default 586 ms ok 223 - tablespace 1554 ms 1..223 # 1 of 223 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/alter_table.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out --- /tmp/cirrus-ci-build/src/test/regress/expected/alter_table.out 2024-05-05 05:17:51.890946000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-05-05 05:19:20.059350000 +0000 @@ -3476,9 +3476,20 @@ WHERE relkind IN ('r', 'i', 'S', 't', 'm') AND mapped_oid IS DISTINCT FROM oid; SELECT m.* FROM filenode_mapping m LEFT JOIN pg_class c ON c.oid = m.oid WHERE c.oid IS NOT NULL OR m.mapped_oid IS NOT NULL; - oid | mapped_oid | reltablespace | relfilenode | relname ------+------------+---------------+-------------+--------- -(0 rows) + oid | mapped_oid | reltablespace | relfilenode | relname +-------+------------+---------------+-------------+---------------------- + 37773 | | 0 | 37773 | pktable_pkey + 37770 | | 0 | 37770 | pktable + 37775 | | 0 | 37775 | fktable + 38400 | | 0 | 38405 | foo + 38409 | | 0 | 38409 | pg_toast_38400_index + 38408 | | 0 | 38408 | pg_toast_38400 + 38671 | | 0 | 38671 | old_oids + 38699 | | 0 | 38699 | pg_toast_38696 + 38700 | | 0 | 38700 | pg_toast_38696_index + 38696 | | 0 | 38696 | recur2 + 38682 | | 0 | 38682 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [05:19:29.491](55.180s) not ok 5 - regression tests pass [05:19:29.492](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [05:19:29.492](0.000s) # got: '256' # expected: '0' # Checking port 57898 # Found port 57898 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=57898 host=/tmp/pEtZgWYjvr Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [05:19:29.497](0.005s) # 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: 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 /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 ... 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=57897 host=/tmp/pEtZgWYjvr dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_NOrK/dump1.sql [05:19:34.618](5.121s) 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/pEtZgWYjvr -p 57897 -P 57898 --link --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 [05:19:34.812](0.194s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [05:19:34.815](0.002s) 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/pEtZgWYjvr -p 57897 -P 57898 --link --check [05:19:35.565](0.750s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [05:19:35.565](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [05:19:35.567](0.002s) 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 18296 ### 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/pEtZgWYjvr -p 57897 -P 57898 --link --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* [05:19:37.259](1.692s) ok 12 - run of pg_upgrade --check for new instance [05:19:37.260](0.001s) 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/pEtZgWYjvr -p 57897 -P 57898 --link 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 Adding ".old" suffix to old global/pg_control ok If you want to start the old cluster, you will need to remove the ".old" suffix from /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata/global/pg_control.old. Because "link" mode was used, the old cluster cannot be safely started once the new cluster has been started. Linking 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 [05:19:57.571](20.311s) ok 14 - run of pg_upgrade for new instance [05:19:57.572](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 22235 [05:19:57.693](0.121s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=57898 host=/tmp/pEtZgWYjvr dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_NOrK/dump2.sql [05:19:59.754](2.060s) ok 17 - dump after running pg_upgrade [05:19:59.835](0.081s) ok 18 - old and new dumps match after pg_upgrade [05:19:59.835](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" [05:19:59.941](0.106s) # Looks like you failed 1 test of 18.