[06:46:31.686](0.027s) # testing using transfer mode --link # Checking port 50618 # Found port 50618 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=50618 host=/tmp/dJBFHRoo9A Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [06:46:31.692](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_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 6095 [06:46:33.787](2.095s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [06:46:33.826](0.040s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [06:46:33.872](0.046s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [06:46:33.912](0.040s) ok 4 - created database with ASCII characters from 91 to 127 [06:46:33.914](0.002s) # running regression tests in old instance # using postmaster on /tmp/dJBFHRoo9A, port 50618 ok 1 - test_setup 507 ms # parallel group (20 tests): varchar char pg_lsn name txid oid text uuid int2 money boolean regproc float4 int4 bit int8 enum float8 rangetypes numeric ok 2 + boolean 339 ms ok 3 + char 145 ms ok 4 + name 215 ms ok 5 + varchar 118 ms ok 6 + text 259 ms ok 7 + int2 286 ms ok 8 + int4 390 ms ok 9 + int8 418 ms ok 10 + oid 236 ms ok 11 + float4 352 ms ok 12 + float8 455 ms ok 13 + bit 397 ms ok 14 + numeric 1089 ms ok 15 + txid 228 ms ok 16 + uuid 272 ms ok 17 + enum 422 ms ok 18 + money 330 ms ok 19 + rangetypes 873 ms ok 20 + pg_lsn 165 ms ok 21 + regproc 348 ms # parallel group (20 tests): lseg md5 circle path line time macaddr timetz point macaddr8 numerology inet polygon date box timestamp interval strings timestamptz multirangetypes ok 22 + strings 715 ms ok 23 + md5 72 ms ok 24 + numerology 216 ms ok 25 + point 139 ms ok 26 + lseg 60 ms ok 27 + line 100 ms ok 28 + box 454 ms ok 29 + path 92 ms ok 30 + polygon 322 ms ok 31 + circle 73 ms ok 32 + date 436 ms ok 33 + time 119 ms ok 34 + timetz 126 ms ok 35 + timestamp 609 ms ok 36 + timestamptz 737 ms ok 37 + interval 658 ms ok 38 + inet 238 ms ok 39 + macaddr 125 ms ok 40 + macaddr8 199 ms ok 41 + multirangetypes 966 ms # parallel group (12 tests): comments mvcc misc_sanity unicode type_sanity xid expressions tstypes regex geometry opr_sanity horology ok 42 + geometry 411 ms ok 43 + horology 460 ms ok 44 + tstypes 346 ms ok 45 + regex 403 ms ok 46 + type_sanity 190 ms ok 47 + opr_sanity 439 ms ok 48 + misc_sanity 129 ms ok 49 + comments 27 ms ok 50 + expressions 315 ms ok 51 + unicode 139 ms ok 52 + xid 282 ms ok 53 + mvcc 80 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 332 ms ok 55 + copyselect 88 ms ok 56 + copydml 105 ms ok 57 + insert 1066 ms ok 58 + insert_conflict 468 ms # parallel group (7 tests): create_function_c create_operator create_misc create_procedure create_schema create_type create_table ok 59 + create_function_c 32 ms ok 60 + create_misc 112 ms ok 61 + create_operator 84 ms ok 62 + create_procedure 127 ms ok 63 + create_table 1187 ms ok 64 + create_type 181 ms ok 65 + create_schema 127 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2563 ms ok 67 + create_index_spgist 1132 ms ok 68 + create_view 1543 ms ok 69 + index_including 752 ms ok 70 + index_including_gist 746 ms # parallel group (16 tests): create_cast roleattributes create_aggregate errors hash_func typed_table infinite_recurse select drop_if_exists create_am create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 179 ms ok 72 + create_function_sql 531 ms ok 73 + create_cast 124 ms ok 74 + constraints 2045 ms ok 75 + triggers 6476 ms ok 76 + select 429 ms ok 77 + inherit 4344 ms ok 78 + typed_table 372 ms ok 79 + vacuum 1144 ms ok 80 + drop_if_exists 517 ms ok 81 + updatable_views 2803 ms ok 82 + roleattributes 173 ms ok 83 + create_am 525 ms ok 84 + hash_func 188 ms ok 85 + errors 183 ms ok 86 + infinite_recurse 400 ms ok 87 - sanity_check 157 ms # parallel group (20 tests): delete select_distinct_on select_having select_implicit random case namespace select_distinct select_into prepared_xacts union hash_index subselect transactions arrays portals update aggregates btree_index join ok 88 + select_into 462 ms ok 89 + select_distinct 436 ms ok 90 + select_distinct_on 83 ms ok 91 + select_implicit 256 ms ok 92 + select_having 152 ms ok 93 + subselect 959 ms ok 94 + union 772 ms ok 95 + case 342 ms ok 96 + join 2214 ms ok 97 + aggregates 1799 ms ok 98 + transactions 1120 ms ok 99 + random 313 ms ok 100 + portals 1334 ms ok 101 + arrays 1288 ms ok 102 + btree_index 2079 ms ok 103 + hash_index 910 ms ok 104 + update 1608 ms ok 105 + delete 79 ms ok 106 + namespace 386 ms ok 107 + prepared_xacts 487 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label password lock object_address groupingsets collate gin replica_identity spgist gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 4093 ms ok 109 + gin 1383 ms ok 110 + gist 1607 ms ok 111 + spgist 1464 ms ok 112 + privileges 4678 ms ok 113 + init_privs 104 ms ok 114 + security_label 509 ms ok 115 + collate 1258 ms ok 116 + matview 2235 ms ok 117 + lock 866 ms ok 118 + replica_identity 1417 ms ok 119 + rowsecurity 4637 ms ok 120 + object_address 917 ms ok 121 + tablesample 395 ms ok 122 + groupingsets 1072 ms ok 123 + drop_operator 200 ms ok 124 + password 796 ms ok 125 + identity 2323 ms ok 126 + generated 3708 ms ok 127 + join_hash 4198 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 172 ms ok 129 + brin_multi 1188 ms # parallel group (18 tests): async dbsize collate.utf8 sysviews tidrangescan tid alter_operator tidscan tsrf misc create_role incremental_sort misc_functions alter_generic create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 1210 ms ok 131 + alter_generic 993 ms ok 132 + alter_operator 363 ms ok 133 + misc 445 ms ok 134 + async 123 ms ok 135 + dbsize 208 ms ok 136 + merge 1514 ms ok 137 + misc_functions 576 ms ok 138 + sysviews 256 ms ok 139 + tsrf 433 ms ok 140 + tid 340 ms ok 141 + tidscan 369 ms ok 142 + tidrangescan 337 ms ok 143 + collate.utf8 213 ms ok 144 + collate.icu.utf8 1257 ms ok 145 + incremental_sort 506 ms ok 146 + create_role 478 ms ok 147 + without_overlaps 2185 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1427 ms ok 149 + psql 1968 ms ok 150 + psql_crosstab 115 ms ok 151 + amutils 41 ms ok 152 + stats_ext 3156 ms ok 153 + collate.linux.utf8 30 ms ok 154 + collate.windows.win1252 19 ms ok 155 - select_parallel 1754 ms ok 156 - write_parallel 148 ms ok 157 - vacuum_parallel 109 ms # parallel group (2 tests): subscription publication ok 158 + publication 2379 ms ok 159 + subscription 102 ms # parallel group (17 tests): advisory_lock portals_p2 functional_deps xmlmap combocid bitmapops dependency indirect_toast equivclass tsdicts select_views guc window cluster tsearch foreign_data foreign_key ok 160 + select_views 727 ms ok 161 + portals_p2 354 ms ok 162 + foreign_key 8307 ms ok 163 + cluster 1600 ms ok 164 + dependency 664 ms ok 165 + guc 856 ms ok 166 + bitmapops 550 ms ok 167 + combocid 486 ms ok 168 + tsearch 1951 ms ok 169 + tsdicts 726 ms ok 170 + foreign_data 3254 ms ok 171 + window 1551 ms ok 172 + xmlmap 400 ms ok 173 + functional_deps 372 ms ok 174 + advisory_lock 341 ms ok 175 + indirect_toast 665 ms ok 176 + equivclass 686 ms # parallel group (9 tests): json_encoding jsonpath_encoding jsonpath sqljson sqljson_jsontable sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 375 ms ok 178 + jsonb 596 ms ok 179 + json_encoding 18 ms ok 180 + jsonpath 134 ms ok 181 + jsonpath_encoding 35 ms ok 182 + jsonb_jsonpath 419 ms ok 183 + sqljson 203 ms ok 184 + sqljson_queryfuncs 259 ms ok 185 + sqljson_jsontable 205 ms # parallel group (18 tests): prepare returning limit conversion plancache temp rowtypes sequence truncate copy2 largeobject polymorphism with xml rangefuncs domain plpgsql alter_table ok 186 + plancache 533 ms ok 187 + limit 385 ms ok 188 + plpgsql 3064 ms ok 189 + copy2 1065 ms ok 190 + temp 837 ms ok 191 + domain 1429 ms ok 192 + rangefuncs 1289 ms ok 193 + prepare 189 ms ok 194 + conversion 390 ms ok 195 + truncate 1058 ms not ok 196 + alter_table 11690 ms ok 197 + sequence 1012 ms ok 198 + polymorphism 1103 ms ok 199 + rowtypes 965 ms ok 200 + returning 296 ms ok 201 + largeobject 1064 ms ok 202 + with 1201 ms ok 203 + xml 1258 ms # parallel group (15 tests): predicate hash_part partition_info reloptions explain memoize compression partition_merge partition_aggregate partition_split stats tuplesort partition_join partition_prune indexing ok 204 + partition_merge 937 ms ok 205 + partition_split 1999 ms ok 206 + partition_join 3253 ms ok 207 + partition_prune 3742 ms ok 208 + reloptions 177 ms ok 209 + hash_part 113 ms ok 210 + indexing 3897 ms ok 211 + partition_aggregate 1902 ms ok 212 + partition_info 177 ms ok 213 + tuplesort 2191 ms ok 214 + explain 240 ms ok 215 + compression 564 ms ok 216 + memoize 347 ms ok 217 + stats 2017 ms ok 218 + predicate 112 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 413 ms ok 220 + event_trigger 651 ms ok 221 - event_trigger_login 155 ms ok 222 - fast_default 725 ms ok 223 - tablespace 1496 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-03 06:45:51.119846000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/alter_table.out 2024-05-03 06:47:27.382899000 +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 +-------+------------+---------------+-------------+---------------------- + 37844 | | 0 | 37844 | pktable_pkey + 37841 | | 0 | 37841 | pktable + 37846 | | 0 | 37846 | fktable + 38353 | | 0 | 38360 | foo + 38364 | | 0 | 38364 | pg_toast_38353_index + 38363 | | 0 | 38363 | pg_toast_38353 + 38591 | | 0 | 38591 | old_oids + 38611 | | 0 | 38611 | pg_toast_38608 + 38612 | | 0 | 38612 | pg_toast_38608_index + 38608 | | 0 | 38608 | recur2 + 38603 | | 0 | 38603 | recur1 +(11 rows) -- Checks on creating and manipulation of user defined relations in -- pg_catalog. === EOF === [06:47:34.446](60.532s) not ok 5 - regression tests pass [06:47:34.446](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [06:47:34.447](0.000s) # got: '256' # expected: '0' # Checking port 50619 # Found port 50619 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=50619 host=/tmp/dJBFHRoo9A Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [06:47:34.450](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=50618 host=/tmp/dJBFHRoo9A dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_9bzH/dump1.sql [06:47:38.936](4.486s) 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/dJBFHRoo9A -p 50618 -P 50619 --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 [06:47:39.088](0.152s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [06:47:39.088](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/dJBFHRoo9A -p 50618 -P 50619 --link --check [06:47:39.783](0.695s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [06:47:39.783](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [06:47:39.784](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 18537 ### 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/dJBFHRoo9A -p 50618 -P 50619 --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* [06:47:41.555](1.771s) ok 12 - run of pg_upgrade --check for new instance [06:47:41.555](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/dJBFHRoo9A -p 50618 -P 50619 --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 [06:48:04.688](23.133s) ok 14 - run of pg_upgrade for new instance [06:48:04.688](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 22776 [06:48:04.813](0.125s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=50619 host=/tmp/dJBFHRoo9A dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_9bzH/dump2.sql [06:48:06.919](2.106s) ok 17 - dump after running pg_upgrade [06:48:07.004](0.085s) ok 18 - old and new dumps match after pg_upgrade [06:48:07.005](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" [06:48:07.113](0.109s) # Looks like you failed 1 test of 18.