[13:45:13.384](0.013s) # testing using transfer mode --link # Checking port 52699 # Found port 52699 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=52699 host=/tmp/h3YxWzILKA Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [13:45:13.437](0.053s) # 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 6010 [13:45:15.353](1.916s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [13:45:15.422](0.069s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [13:45:15.476](0.054s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [13:45:15.526](0.051s) ok 4 - created database with ASCII characters from 91 to 127 [13:45:15.528](0.002s) # running regression tests in old instance # using postmaster on /tmp/h3YxWzILKA, port 52699 ok 1 - test_setup 305 ms # parallel group (20 tests): varchar char pg_lsn oid name txid uuid text float4 regproc money int2 int4 boolean float8 int8 bit enum rangetypes numeric ok 2 + boolean 299 ms ok 3 + char 142 ms ok 4 + name 171 ms ok 5 + varchar 124 ms ok 6 + text 213 ms ok 7 + int2 281 ms ok 8 + int4 283 ms ok 9 + int8 339 ms ok 10 + oid 146 ms ok 11 + float4 242 ms ok 12 + float8 326 ms ok 13 + bit 342 ms ok 14 + numeric 935 ms ok 15 + txid 203 ms ok 16 + uuid 205 ms ok 17 + enum 395 ms ok 18 + money 275 ms ok 19 + rangetypes 764 ms ok 20 + pg_lsn 143 ms ok 21 + regproc 250 ms # parallel group (20 tests): md5 lseg path circle line timetz time point macaddr numerology macaddr8 polygon inet date box interval timestamp timestamptz multirangetypes strings ok 22 + strings 686 ms ok 23 + md5 55 ms ok 24 + numerology 262 ms ok 25 + point 197 ms ok 26 + lseg 69 ms ok 27 + line 126 ms ok 28 + box 402 ms ok 29 + path 74 ms ok 30 + polygon 312 ms ok 31 + circle 78 ms ok 32 + date 354 ms ok 33 + time 178 ms ok 34 + timetz 125 ms ok 35 + timestamp 488 ms ok 36 + timestamptz 649 ms ok 37 + interval 419 ms ok 38 + inet 326 ms ok 39 + macaddr 256 ms ok 40 + macaddr8 276 ms ok 41 + multirangetypes 679 ms # parallel group (12 tests): misc_sanity comments unicode mvcc type_sanity tstypes xid regex geometry expressions horology opr_sanity ok 42 + geometry 312 ms ok 43 + horology 435 ms ok 44 + tstypes 175 ms ok 45 + regex 308 ms ok 46 + type_sanity 130 ms ok 47 + opr_sanity 446 ms ok 48 + misc_sanity 37 ms ok 49 + comments 37 ms ok 50 + expressions 328 ms ok 51 + unicode 48 ms ok 52 + xid 193 ms ok 53 + mvcc 72 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 365 ms ok 55 + copyselect 138 ms ok 56 + copydml 122 ms ok 57 + insert 1453 ms ok 58 + insert_conflict 603 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 31 ms ok 60 + create_misc 165 ms ok 61 + create_operator 126 ms ok 62 + create_procedure 169 ms ok 63 + create_table 1308 ms ok 64 + create_type 168 ms ok 65 + create_schema 117 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2264 ms ok 67 + create_index_spgist 1005 ms ok 68 + create_view 1311 ms ok 69 + index_including 908 ms ok 70 + index_including_gist 526 ms # parallel group (16 tests): create_cast hash_func select errors create_aggregate roleattributes drop_if_exists infinite_recurse typed_table create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 202 ms ok 72 + create_function_sql 499 ms ok 73 + create_cast 107 ms ok 74 + constraints 1845 ms ok 75 + triggers 5669 ms ok 76 + select 196 ms ok 77 + inherit 4003 ms ok 78 + typed_table 479 ms ok 79 + vacuum 1044 ms ok 80 + drop_if_exists 357 ms ok 81 + updatable_views 3178 ms ok 82 + roleattributes 214 ms ok 83 + create_am 524 ms ok 84 + hash_func 159 ms ok 85 + errors 196 ms ok 86 + infinite_recurse 363 ms ok 87 - sanity_check 199 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit random case namespace select_into prepared_xacts select_distinct union portals transactions subselect arrays hash_index update aggregates btree_index join ok 88 + select_into 324 ms ok 89 + select_distinct 386 ms ok 90 + select_distinct_on 84 ms ok 91 + select_implicit 214 ms ok 92 + select_having 121 ms ok 93 + subselect 856 ms ok 94 + union 625 ms ok 95 + case 224 ms ok 96 + join 2146 ms ok 97 + aggregates 1558 ms ok 98 + transactions 776 ms ok 99 + random 214 ms ok 100 + portals 676 ms ok 101 + arrays 913 ms ok 102 + btree_index 1989 ms ok 103 + hash_index 1166 ms ok 104 + update 1451 ms ok 105 + delete 88 ms ok 106 + namespace 230 ms ok 107 + prepared_xacts 350 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label password lock collate groupingsets object_address gist spgist replica_identity gin matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 3721 ms ok 109 + gin 1616 ms ok 110 + gist 1477 ms ok 111 + spgist 1515 ms ok 112 + privileges 4499 ms ok 113 + init_privs 90 ms ok 114 + security_label 492 ms ok 115 + collate 1247 ms ok 116 + matview 2665 ms ok 117 + lock 1125 ms ok 118 + replica_identity 1530 ms ok 119 + rowsecurity 3972 ms ok 120 + object_address 1426 ms ok 121 + tablesample 486 ms ok 122 + groupingsets 1424 ms ok 123 + drop_operator 315 ms ok 124 + password 776 ms ok 125 + identity 2727 ms ok 126 + generated 3469 ms ok 127 + join_hash 3795 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 159 ms ok 129 + brin_multi 712 ms # parallel group (18 tests): async collate.utf8 dbsize sysviews tid tidrangescan tidscan 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 1058 ms ok 131 + alter_generic 575 ms ok 132 + alter_operator 320 ms ok 133 + misc 303 ms ok 134 + async 56 ms ok 135 + dbsize 122 ms ok 136 + merge 1172 ms ok 137 + misc_functions 367 ms ok 138 + sysviews 185 ms ok 139 + tsrf 263 ms ok 140 + tid 205 ms ok 141 + tidscan 240 ms ok 142 + tidrangescan 217 ms ok 143 + collate.utf8 89 ms ok 144 + collate.icu.utf8 1159 ms ok 145 + incremental_sort 463 ms ok 146 + create_role 495 ms ok 147 + without_overlaps 1506 ms # parallel group (7 tests): collate.linux.utf8 amutils psql_crosstab collate.windows.win1252 rules psql stats_ext ok 148 + rules 1996 ms ok 149 + psql 2031 ms ok 150 + psql_crosstab 67 ms ok 151 + amutils 53 ms ok 152 + stats_ext 3662 ms ok 153 + collate.linux.utf8 34 ms ok 154 + collate.windows.win1252 72 ms ok 155 - select_parallel 2173 ms ok 156 - write_parallel 156 ms ok 157 - vacuum_parallel 101 ms # parallel group (2 tests): subscription publication ok 158 + publication 1050 ms ok 159 + subscription 78 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap functional_deps combocid tsdicts dependency equivclass select_views bitmapops guc indirect_toast tsearch window cluster foreign_data foreign_key ok 160 + select_views 418 ms ok 161 + portals_p2 96 ms ok 162 + foreign_key 6581 ms ok 163 + cluster 1135 ms ok 164 + dependency 385 ms ok 165 + guc 456 ms ok 166 + bitmapops 444 ms ok 167 + combocid 303 ms ok 168 + tsearch 773 ms ok 169 + tsdicts 330 ms ok 170 + foreign_data 2789 ms ok 171 + window 824 ms ok 172 + xmlmap 228 ms ok 173 + functional_deps 270 ms ok 174 + advisory_lock 134 ms ok 175 + indirect_toast 500 ms ok 176 + equivclass 402 ms # parallel group (9 tests): json_encoding jsonpath_encoding jsonpath sqljson sqljson_jsontable sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 381 ms ok 178 + jsonb 750 ms ok 179 + json_encoding 66 ms ok 180 + jsonpath 202 ms ok 181 + jsonpath_encoding 66 ms ok 182 + jsonb_jsonpath 498 ms ok 183 + sqljson 202 ms ok 184 + sqljson_queryfuncs 338 ms ok 185 + sqljson_jsontable 277 ms # parallel group (18 tests): prepare returning limit conversion plancache temp rowtypes with sequence truncate polymorphism rangefuncs copy2 xml largeobject domain plpgsql alter_table ok 186 + plancache 472 ms ok 187 + limit 376 ms ok 188 + plpgsql 2710 ms ok 189 + copy2 1284 ms ok 190 + temp 808 ms ok 191 + domain 1502 ms ok 192 + rangefuncs 1266 ms ok 193 + prepare 140 ms ok 194 + conversion 457 ms ok 195 + truncate 1125 ms not ok 196 + alter_table 8796 ms ok 197 + sequence 1053 ms ok 198 + polymorphism 1217 ms ok 199 + rowtypes 949 ms ok 200 + returning 264 ms ok 201 + largeobject 1351 ms ok 202 + with 1039 ms ok 203 + xml 1318 ms # parallel group (15 tests): reloptions hash_part predicate partition_info explain memoize compression partition_merge partition_aggregate tuplesort stats partition_split partition_prune partition_join indexing ok 204 + partition_merge 2393 ms ok 205 + partition_split 3873 ms ok 206 + partition_join 4928 ms ok 207 + partition_prune 4854 ms ok 208 + reloptions 90 ms ok 209 + hash_part 116 ms ok 210 + indexing 5164 ms ok 211 + partition_aggregate 2497 ms ok 212 + partition_info 525 ms ok 213 + tuplesort 3049 ms ok 214 + explain 599 ms ok 215 + compression 1490 ms ok 216 + memoize 665 ms ok 217 + stats 3191 ms ok 218 + predicate 176 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 308 ms ok 220 + event_trigger 423 ms ok 221 - event_trigger_login 40 ms ok 222 - fast_default 424 ms ok 223 - tablespace 2051 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-04-27 13:44:34.766048000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-27 13:46:01.531401000 +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 +-------+------------+---------------+-------------+---------------------- + 37839 | | 0 | 37839 | pktable_pkey + 37835 | | 0 | 37835 | pktable + 37841 | | 0 | 37841 | fktable + 38387 | | 0 | 38393 | foo + 38397 | | 0 | 38397 | pg_toast_38387_index + 38396 | | 0 | 38396 | pg_toast_38387 + 38670 | | 0 | 38670 | old_oids + 38687 | | 0 | 38687 | pg_toast_38684 + 38688 | | 0 | 38688 | pg_toast_38684_index + 38684 | | 0 | 38684 | recur2 + 38679 | | 0 | 38679 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [13:46:09.704](54.176s) not ok 5 - regression tests pass [13:46:09.704](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [13:46:09.704](0.000s) # got: '256' # expected: '0' # Checking port 52700 # Found port 52700 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=52700 host=/tmp/h3YxWzILKA Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [13:46:09.707](0.003s) # 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=52699 host=/tmp/h3YxWzILKA dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_ufcS/dump1.sql [13:46:14.071](4.364s) 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/h3YxWzILKA -p 52699 -P 52700 --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 [13:46:14.281](0.210s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [13:46:14.282](0.001s) 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/h3YxWzILKA -p 52699 -P 52700 --link --check [13:46:15.023](0.740s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [13:46:15.023](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [13:46:15.023](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 18255 ### 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/h3YxWzILKA -p 52699 -P 52700 --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* [13:46:16.810](1.787s) ok 12 - run of pg_upgrade --check for new instance [13:46:16.811](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/h3YxWzILKA -p 52699 -P 52700 --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 [13:46:36.088](19.278s) ok 14 - run of pg_upgrade for new instance [13:46:36.088](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 21985 [13:46:36.215](0.126s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=52700 host=/tmp/h3YxWzILKA dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_ufcS/dump2.sql [13:46:38.370](2.155s) ok 17 - dump after running pg_upgrade [13:46:38.449](0.080s) ok 18 - old and new dumps match after pg_upgrade [13:46:38.450](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" [13:46:38.558](0.109s) # Looks like you failed 1 test of 18.