[00:31:31.813](0.023s) # testing using transfer mode --link # Checking port 61027 # Found port 61027 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=61027 host=/tmp/D4Rf4hStVP Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [00:31:31.857](0.044s) # 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 6055 [00:31:34.414](2.557s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [00:31:34.472](0.058s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [00:31:34.529](0.057s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [00:31:34.576](0.047s) ok 4 - created database with ASCII characters from 91 to 127 [00:31:34.577](0.001s) # running regression tests in old instance # using postmaster on /tmp/D4Rf4hStVP, port 61027 ok 1 - test_setup 815 ms # parallel group (20 tests): varchar char pg_lsn txid name oid uuid int2 text regproc float4 money boolean int4 int8 bit enum float8 rangetypes numeric ok 2 + boolean 242 ms ok 3 + char 122 ms ok 4 + name 168 ms ok 5 + varchar 102 ms ok 6 + text 199 ms ok 7 + int2 198 ms ok 8 + int4 256 ms ok 9 + int8 261 ms ok 10 + oid 168 ms ok 11 + float4 224 ms ok 12 + float8 302 ms ok 13 + bit 283 ms ok 14 + numeric 1259 ms ok 15 + txid 150 ms ok 16 + uuid 172 ms ok 17 + enum 298 ms ok 18 + money 234 ms ok 19 + rangetypes 867 ms ok 20 + pg_lsn 133 ms ok 21 + regproc 209 ms # parallel group (20 tests): lseg md5 point path circle line macaddr time macaddr8 timetz numerology polygon inet date interval box timestamp timestamptz strings multirangetypes ok 22 + strings 732 ms ok 23 + md5 135 ms ok 24 + numerology 259 ms ok 25 + point 145 ms ok 26 + lseg 127 ms ok 27 + line 168 ms ok 28 + box 511 ms ok 29 + path 145 ms ok 30 + polygon 346 ms ok 31 + circle 155 ms ok 32 + date 367 ms ok 33 + time 224 ms ok 34 + timetz 236 ms ok 35 + timestamp 566 ms ok 36 + timestamptz 656 ms ok 37 + interval 474 ms ok 38 + inet 348 ms ok 39 + macaddr 173 ms ok 40 + macaddr8 229 ms ok 41 + multirangetypes 860 ms # parallel group (12 tests): unicode misc_sanity comments mvcc expressions type_sanity xid geometry tstypes horology opr_sanity regex ok 42 + geometry 315 ms ok 43 + horology 409 ms ok 44 + tstypes 402 ms ok 45 + regex 564 ms ok 46 + type_sanity 271 ms ok 47 + opr_sanity 548 ms ok 48 + misc_sanity 64 ms ok 49 + comments 79 ms ok 50 + expressions 244 ms ok 51 + unicode 61 ms ok 52 + xid 281 ms ok 53 + mvcc 109 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 316 ms ok 55 + copyselect 76 ms ok 56 + copydml 123 ms ok 57 + insert 1422 ms ok 58 + insert_conflict 851 ms # parallel group (7 tests): create_function_c create_operator create_type create_schema create_misc create_procedure create_table ok 59 + create_function_c 24 ms ok 60 + create_misc 158 ms ok 61 + create_operator 94 ms ok 62 + create_procedure 161 ms ok 63 + create_table 2134 ms ok 64 + create_type 130 ms ok 65 + create_schema 135 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2481 ms ok 67 + create_index_spgist 997 ms ok 68 + create_view 1255 ms ok 69 + index_including 684 ms ok 70 + index_including_gist 558 ms # parallel group (16 tests): create_cast hash_func errors select roleattributes create_aggregate typed_table drop_if_exists infinite_recurse create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 332 ms ok 72 + create_function_sql 618 ms ok 73 + create_cast 116 ms ok 74 + constraints 2887 ms ok 75 + triggers 8155 ms ok 76 + select 220 ms ok 77 + inherit 6904 ms ok 78 + typed_table 413 ms ok 79 + vacuum 1027 ms ok 80 + drop_if_exists 483 ms ok 81 + updatable_views 4240 ms ok 82 + roleattributes 255 ms ok 83 + create_am 564 ms ok 84 + hash_func 153 ms ok 85 + errors 180 ms ok 86 + infinite_recurse 491 ms ok 87 - sanity_check 105 ms # parallel group (20 tests): delete select_distinct_on select_having select_implicit random case select_distinct select_into namespace prepared_xacts union portals transactions subselect arrays hash_index update btree_index aggregates join ok 88 + select_into 497 ms ok 89 + select_distinct 467 ms ok 90 + select_distinct_on 137 ms ok 91 + select_implicit 355 ms ok 92 + select_having 232 ms ok 93 + subselect 1245 ms ok 94 + union 895 ms ok 95 + case 456 ms ok 96 + join 3776 ms ok 97 + aggregates 3255 ms ok 98 + transactions 1188 ms ok 99 + random 452 ms ok 100 + portals 1015 ms ok 101 + arrays 1275 ms ok 102 + btree_index 2952 ms ok 103 + hash_index 1678 ms ok 104 + update 2910 ms ok 105 + delete 94 ms ok 106 + namespace 494 ms ok 107 + prepared_xacts 657 ms # parallel group (20 tests): drop_operator init_privs security_label tablesample password object_address lock spgist groupingsets replica_identity collate gin gist brin matview identity privileges generated join_hash rowsecurity ok 108 + brin 2121 ms ok 109 + gin 1929 ms ok 110 + gist 2041 ms ok 111 + spgist 1525 ms ok 112 + privileges 3970 ms ok 113 + init_privs 202 ms ok 114 + security_label 746 ms ok 115 + collate 1730 ms ok 116 + matview 2870 ms ok 117 + lock 1280 ms ok 118 + replica_identity 1661 ms ok 119 + rowsecurity 5901 ms ok 120 + object_address 1178 ms ok 121 + tablesample 765 ms ok 122 + groupingsets 1527 ms ok 123 + drop_operator 142 ms ok 124 + password 1010 ms ok 125 + identity 3285 ms ok 126 + generated 4677 ms ok 127 + join_hash 5179 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 168 ms ok 129 + brin_multi 837 ms # parallel group (18 tests): async collate.utf8 dbsize tidrangescan sysviews tidscan tid tsrf misc alter_operator misc_functions incremental_sort create_role alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 2284 ms ok 131 + alter_generic 1267 ms ok 132 + alter_operator 701 ms ok 133 + misc 677 ms ok 134 + async 156 ms ok 135 + dbsize 306 ms ok 136 + merge 2378 ms ok 137 + misc_functions 707 ms ok 138 + sysviews 355 ms ok 139 + tsrf 611 ms ok 140 + tid 515 ms ok 141 + tidscan 435 ms ok 142 + tidrangescan 326 ms ok 143 + collate.utf8 256 ms ok 144 + collate.icu.utf8 1782 ms ok 145 + incremental_sort 938 ms ok 146 + create_role 950 ms ok 147 + without_overlaps 3588 ms # parallel group (7 tests): psql_crosstab collate.windows.win1252 collate.linux.utf8 amutils rules psql stats_ext ok 148 + rules 1880 ms ok 149 + psql 2184 ms ok 150 + psql_crosstab 49 ms ok 151 + amutils 78 ms ok 152 + stats_ext 3915 ms ok 153 + collate.linux.utf8 64 ms ok 154 + collate.windows.win1252 54 ms ok 155 - select_parallel 2196 ms ok 156 - write_parallel 215 ms ok 157 - vacuum_parallel 129 ms # parallel group (2 tests): subscription publication ok 158 + publication 1806 ms ok 159 + subscription 130 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap combocid functional_deps select_views dependency bitmapops indirect_toast equivclass guc tsdicts cluster window tsearch foreign_data foreign_key ok 160 + select_views 744 ms ok 161 + portals_p2 250 ms ok 162 + foreign_key 9398 ms ok 163 + cluster 1820 ms ok 164 + dependency 770 ms ok 165 + guc 997 ms ok 166 + bitmapops 819 ms ok 167 + combocid 415 ms ok 168 + tsearch 2118 ms ok 169 + tsdicts 1056 ms ok 170 + foreign_data 4530 ms ok 171 + window 2001 ms ok 172 + xmlmap 391 ms ok 173 + functional_deps 483 ms ok 174 + advisory_lock 319 ms ok 175 + indirect_toast 861 ms ok 176 + equivclass 981 ms # parallel group (9 tests): json_encoding jsonpath_encoding jsonpath sqljson sqljson_jsontable sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 393 ms ok 178 + jsonb 678 ms ok 179 + json_encoding 61 ms ok 180 + jsonpath 127 ms ok 181 + jsonpath_encoding 94 ms ok 182 + jsonb_jsonpath 456 ms ok 183 + sqljson 177 ms ok 184 + sqljson_queryfuncs 350 ms ok 185 + sqljson_jsontable 296 ms # parallel group (18 tests): prepare returning conversion limit plancache temp truncate sequence rowtypes copy2 largeobject with xml polymorphism rangefuncs domain plpgsql alter_table ok 186 + plancache 476 ms ok 187 + limit 433 ms ok 188 + plpgsql 4672 ms ok 189 + copy2 1027 ms ok 190 + temp 605 ms ok 191 + domain 1555 ms ok 192 + rangefuncs 1317 ms ok 193 + prepare 140 ms ok 194 + conversion 294 ms ok 195 + truncate 882 ms not ok 196 + alter_table 14736 ms ok 197 + sequence 931 ms ok 198 + polymorphism 1295 ms ok 199 + rowtypes 944 ms ok 200 + returning 286 ms ok 201 + largeobject 1141 ms ok 202 + with 1180 ms ok 203 + xml 1201 ms # parallel group (15 tests): predicate memoize explain partition_info hash_part reloptions compression partition_merge partition_split stats partition_aggregate tuplesort partition_join indexing partition_prune ok 204 + partition_merge 954 ms ok 205 + partition_split 1309 ms ok 206 + partition_join 4332 ms ok 207 + partition_prune 4473 ms ok 208 + reloptions 467 ms ok 209 + hash_part 466 ms ok 210 + indexing 4468 ms ok 211 + partition_aggregate 2140 ms ok 212 + partition_info 466 ms ok 213 + tuplesort 3020 ms ok 214 + explain 465 ms ok 215 + compression 697 ms ok 216 + memoize 465 ms ok 217 + stats 2026 ms ok 218 + predicate 339 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 404 ms ok 220 + event_trigger 462 ms ok 221 - event_trigger_login 41 ms ok 222 - fast_default 612 ms ok 223 - tablespace 1413 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-22 00:30:48.623187000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-04-22 00:32:40.489361000 +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 +-------+------------+---------------+-------------+---------------------- + 37790 | | 0 | 37790 | pktable_pkey + 37787 | | 0 | 37787 | pktable + 37794 | | 0 | 37794 | fktable + 38327 | | 0 | 38332 | foo + 38336 | | 0 | 38336 | pg_toast_38327_index + 38335 | | 0 | 38335 | pg_toast_38327 + 38550 | | 0 | 38550 | old_oids + 38567 | | 0 | 38567 | pg_toast_38564 + 38568 | | 0 | 38568 | pg_toast_38564_index + 38564 | | 0 | 38564 | recur2 + 38559 | | 0 | 38559 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [00:32:47.616](73.039s) not ok 5 - regression tests pass [00:32:47.616](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [00:32:47.616](0.000s) # got: '256' # expected: '0' # Checking port 61028 # Found port 61028 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=61028 host=/tmp/D4Rf4hStVP Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [00:32:47.619](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=61027 host=/tmp/D4Rf4hStVP dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_A9px/dump1.sql [00:32:51.508](3.888s) 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/D4Rf4hStVP -p 61027 -P 61028 --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 [00:32:51.656](0.148s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [00:32:51.656](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/D4Rf4hStVP -p 61027 -P 61028 --link --check [00:32:52.451](0.795s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [00:32:52.452](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [00:32:52.452](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 18708 ### 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/D4Rf4hStVP -p 61027 -P 61028 --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* [00:32:54.757](2.305s) ok 12 - run of pg_upgrade --check for new instance [00:32:54.758](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/D4Rf4hStVP -p 61027 -P 61028 --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 [00:33:16.782](22.024s) ok 14 - run of pg_upgrade for new instance [00:33:16.782](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 22859 [00:33:16.914](0.131s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=61028 host=/tmp/D4Rf4hStVP dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_A9px/dump2.sql [00:33:19.024](2.110s) ok 17 - dump after running pg_upgrade [00:33:19.118](0.094s) ok 18 - old and new dumps match after pg_upgrade [00:33:19.118](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" [00:33:19.229](0.111s) # Looks like you failed 1 test of 18.