[05:38:51.272](0.013s) # testing using transfer mode --link # Checking port 50598 # Found port 50598 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=50598 host=/tmp/2N22PCd97z Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [05:38:51.333](0.061s) # 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 6190 [05:38:53.548](2.216s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [05:38:53.627](0.078s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [05:38:53.715](0.088s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [05:38:53.751](0.036s) ok 4 - created database with ASCII characters from 91 to 127 [05:38:53.752](0.001s) # running regression tests in old instance # using postmaster on /tmp/2N22PCd97z, port 50598 ok 1 - test_setup 550 ms # parallel group (20 tests): varchar name char oid pg_lsn txid uuid text int2 int4 regproc boolean float4 money float8 bit int8 enum rangetypes numeric ok 2 + boolean 250 ms ok 3 + char 141 ms ok 4 + name 130 ms ok 5 + varchar 99 ms ok 6 + text 192 ms ok 7 + int2 207 ms ok 8 + int4 242 ms ok 9 + int8 368 ms ok 10 + oid 153 ms ok 11 + float4 253 ms ok 12 + float8 334 ms ok 13 + bit 337 ms ok 14 + numeric 901 ms ok 15 + txid 169 ms ok 16 + uuid 187 ms ok 17 + enum 387 ms ok 18 + money 267 ms ok 19 + rangetypes 772 ms ok 20 + pg_lsn 167 ms ok 21 + regproc 243 ms # parallel group (20 tests): md5 lseg point line macaddr circle time path timetz macaddr8 numerology date polygon inet box timestamp interval timestamptz strings multirangetypes ok 22 + strings 819 ms ok 23 + md5 73 ms ok 24 + numerology 277 ms ok 25 + point 103 ms ok 26 + lseg 86 ms ok 27 + line 112 ms ok 28 + box 528 ms ok 29 + path 153 ms ok 30 + polygon 435 ms ok 31 + circle 118 ms ok 32 + date 423 ms ok 33 + time 130 ms ok 34 + timetz 172 ms ok 35 + timestamp 638 ms ok 36 + timestamptz 737 ms ok 37 + interval 687 ms ok 38 + inet 456 ms ok 39 + macaddr 114 ms ok 40 + macaddr8 271 ms ok 41 + multirangetypes 956 ms # parallel group (12 tests): comments misc_sanity unicode mvcc xid type_sanity expressions geometry tstypes regex horology opr_sanity ok 42 + geometry 330 ms ok 43 + horology 415 ms ok 44 + tstypes 340 ms ok 45 + regex 413 ms ok 46 + type_sanity 200 ms ok 47 + opr_sanity 462 ms ok 48 + misc_sanity 46 ms ok 49 + comments 38 ms ok 50 + expressions 256 ms ok 51 + unicode 68 ms ok 52 + xid 188 ms ok 53 + mvcc 95 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 333 ms ok 55 + copyselect 118 ms ok 56 + copydml 126 ms ok 57 + insert 1280 ms ok 58 + insert_conflict 821 ms # parallel group (7 tests): create_function_c create_operator create_type create_procedure create_schema create_misc create_table ok 59 + create_function_c 24 ms ok 60 + create_misc 227 ms ok 61 + create_operator 78 ms ok 62 + create_procedure 114 ms ok 63 + create_table 2163 ms ok 64 + create_type 97 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 1818 ms ok 67 + create_index_spgist 788 ms ok 68 + create_view 1077 ms ok 69 + index_including 441 ms ok 70 + index_including_gist 404 ms # parallel group (16 tests): errors create_cast typed_table create_aggregate select roleattributes hash_func drop_if_exists infinite_recurse create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 252 ms ok 72 + create_function_sql 478 ms ok 73 + create_cast 99 ms ok 74 + constraints 1593 ms ok 75 + triggers 6220 ms ok 76 + select 258 ms ok 77 + inherit 4088 ms ok 78 + typed_table 245 ms ok 79 + vacuum 996 ms ok 80 + drop_if_exists 401 ms ok 81 + updatable_views 3549 ms ok 82 + roleattributes 265 ms ok 83 + create_am 489 ms ok 84 + hash_func 324 ms ok 85 + errors 73 ms ok 86 + infinite_recurse 452 ms ok 87 - sanity_check 139 ms # parallel group (20 tests): select_distinct_on delete select_having select_implicit random case namespace select_distinct select_into prepared_xacts union portals subselect hash_index arrays transactions update btree_index aggregates join ok 88 + select_into 444 ms ok 89 + select_distinct 439 ms ok 90 + select_distinct_on 91 ms ok 91 + select_implicit 239 ms ok 92 + select_having 175 ms ok 93 + subselect 1090 ms ok 94 + union 876 ms ok 95 + case 346 ms ok 96 + join 2434 ms ok 97 + aggregates 2203 ms ok 98 + transactions 1310 ms ok 99 + random 239 ms ok 100 + portals 1056 ms ok 101 + arrays 1285 ms ok 102 + btree_index 2098 ms ok 103 + hash_index 1096 ms ok 104 + update 1617 ms ok 105 + delete 123 ms ok 106 + namespace 381 ms ok 107 + prepared_xacts 453 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock object_address spgist groupingsets replica_identity collate gin gist matview identity brin join_hash privileges generated rowsecurity ok 108 + brin 4203 ms ok 109 + gin 1537 ms ok 110 + gist 1625 ms ok 111 + spgist 1292 ms ok 112 + privileges 4939 ms ok 113 + init_privs 43 ms ok 114 + security_label 285 ms ok 115 + collate 1476 ms ok 116 + matview 2312 ms ok 117 + lock 1012 ms ok 118 + replica_identity 1422 ms ok 119 + rowsecurity 5382 ms ok 120 + object_address 1282 ms ok 121 + tablesample 732 ms ok 122 + groupingsets 1389 ms ok 123 + drop_operator 188 ms ok 124 + password 771 ms ok 125 + identity 2929 ms ok 126 + generated 5129 ms ok 127 + join_hash 4338 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 145 ms ok 129 + brin_multi 700 ms # parallel group (18 tests): dbsize async collate.utf8 sysviews tidscan tid tidrangescan tsrf alter_operator misc_functions misc create_role incremental_sort alter_generic collate.icu.utf8 merge create_table_like without_overlaps ok 130 + create_table_like 1362 ms ok 131 + alter_generic 711 ms ok 132 + alter_operator 349 ms ok 133 + misc 410 ms ok 134 + async 100 ms ok 135 + dbsize 93 ms ok 136 + merge 1246 ms ok 137 + misc_functions 407 ms ok 138 + sysviews 184 ms ok 139 + tsrf 323 ms ok 140 + tid 233 ms ok 141 + tidscan 206 ms ok 142 + tidrangescan 278 ms ok 143 + collate.utf8 146 ms ok 144 + collate.icu.utf8 1057 ms ok 145 + incremental_sort 447 ms ok 146 + create_role 441 ms ok 147 + without_overlaps 1822 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab rules psql stats_ext ok 148 + rules 1923 ms ok 149 + psql 1955 ms ok 150 + psql_crosstab 109 ms ok 151 + amutils 64 ms ok 152 + stats_ext 3522 ms ok 153 + collate.linux.utf8 15 ms ok 154 + collate.windows.win1252 25 ms ok 155 - select_parallel 1657 ms ok 156 - write_parallel 156 ms ok 157 - vacuum_parallel 116 ms # parallel group (2 tests): subscription publication ok 158 + publication 1795 ms not ok 159 + subscription 156 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap combocid functional_deps equivclass select_views dependency indirect_toast bitmapops tsdicts guc window cluster tsearch foreign_data foreign_key ok 160 + select_views 461 ms ok 161 + portals_p2 104 ms ok 162 + foreign_key 7665 ms ok 163 + cluster 1555 ms ok 164 + dependency 593 ms ok 165 + guc 713 ms ok 166 + bitmapops 642 ms ok 167 + combocid 317 ms ok 168 + tsearch 1626 ms ok 169 + tsdicts 678 ms ok 170 + foreign_data 3021 ms ok 171 + window 1312 ms ok 172 + xmlmap 169 ms ok 173 + functional_deps 364 ms ok 174 + advisory_lock 144 ms ok 175 + indirect_toast 602 ms ok 176 + equivclass 434 ms # parallel group (8 tests): jsonpath_encoding json_encoding sqljson sqljson_queryfuncs jsonpath json jsonb_jsonpath jsonb ok 177 + json 317 ms ok 178 + jsonb 596 ms ok 179 + json_encoding 59 ms ok 180 + jsonpath 283 ms ok 181 + jsonpath_encoding 40 ms ok 182 + jsonb_jsonpath 490 ms ok 183 + sqljson 162 ms ok 184 + sqljson_queryfuncs 258 ms # parallel group (18 tests): prepare conversion limit returning plancache temp sequence rowtypes with truncate copy2 largeobject xml rangefuncs polymorphism domain plpgsql alter_table ok 185 + plancache 575 ms ok 186 + limit 381 ms ok 187 + plpgsql 3409 ms ok 188 + copy2 1139 ms ok 189 + temp 718 ms ok 190 + domain 1475 ms ok 191 + rangefuncs 1357 ms ok 192 + prepare 159 ms ok 193 + conversion 283 ms ok 194 + truncate 1100 ms ok 195 + alter_table 9996 ms ok 196 + sequence 841 ms ok 197 + polymorphism 1372 ms ok 198 + rowtypes 920 ms ok 199 + returning 463 ms ok 200 + largeobject 1256 ms ok 201 + with 1091 ms ok 202 + xml 1263 ms # parallel group (13 tests): predicate reloptions hash_part explain partition_info memoize compression stats partition_aggregate tuplesort partition_join partition_prune indexing ok 203 + partition_join 4405 ms ok 204 + partition_prune 5157 ms ok 205 + reloptions 83 ms ok 206 + hash_part 153 ms ok 207 + indexing 5690 ms ok 208 + partition_aggregate 2293 ms ok 209 + partition_info 277 ms ok 210 + tuplesort 2726 ms ok 211 + explain 277 ms ok 212 + compression 1537 ms ok 213 + memoize 300 ms ok 214 + stats 2269 ms ok 215 + predicate 71 ms # parallel group (2 tests): oidjoins event_trigger ok 216 + oidjoins 628 ms ok 217 + event_trigger 845 ms ok 218 - event_trigger_login 90 ms ok 219 - fast_default 635 ms ok 220 - tablespace 1409 ms 1..220 # 1 of 220 tests failed. # The differences that caused some tests to fail can be viewed in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs". # A copy of the test summary that you see above is saved in the file "/tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.out". === dumping /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/regression.diffs === diff -U3 /tmp/cirrus-ci-build/src/test/regress/expected/subscription.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out --- /tmp/cirrus-ci-build/src/test/regress/expected/subscription.out 2024-04-04 05:38:06.836312000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subscription.out 2024-04-04 05:39:24.781552000 +0000 @@ -381,14 +381,13 @@ --fail - alter of two_phase option not supported. ALTER SUBSCRIPTION regress_testsub SET (two_phase = false); -ERROR: unrecognized subscription parameter: "two_phase" -- but can alter streaming when two_phase enabled ALTER SUBSCRIPTION regress_testsub SET (streaming = true); \dRs+ List of subscriptions Name | Owner | Enabled | Publication | Binary | Streaming | Two-phase commit | Disable on error | Origin | Password required | Run as owner? | Failover | Synchronous commit | Conninfo | Skip LSN -----------------+---------------------------+---------+-------------+--------+-----------+------------------+------------------+--------+-------------------+---------------+----------+--------------------+-----------------------------+---------- - regress_testsub | regress_subscription_user | f | {testpub} | f | on | p | f | any | t | f | f | off | dbname=regress_doesnotexist | 0/0 + regress_testsub | regress_subscription_user | f | {testpub} | f | on | d | f | any | t | f | f | off | dbname=regress_doesnotexist | 0/0 (1 row) ALTER SUBSCRIPTION regress_testsub SET (slot_name = NONE); === EOF === [05:39:53.611](59.860s) not ok 5 - regression tests pass [05:39:53.612](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 260. [05:39:53.612](0.000s) # got: '256' # expected: '0' # Checking port 50599 # Found port 50599 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=50599 host=/tmp/2N22PCd97z Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [05:39:53.615](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=50598 host=/tmp/2N22PCd97z dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_g3Le/dump1.sql [05:39:58.377](4.762s) 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/2N22PCd97z -p 50598 -P 50599 --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:39:58.562](0.184s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [05:39:58.563](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/2N22PCd97z -p 50598 -P 50599 --link --check [05:39:59.163](0.599s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [05:39:59.163](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [05:39:59.164](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 18730 ### 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/2N22PCd97z -p 50598 -P 50599 --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:40:01.651](2.487s) ok 12 - run of pg_upgrade --check for new instance [05:40:01.655](0.005s) 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/2N22PCd97z -p 50598 -P 50599 --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:40:22.760](21.105s) ok 14 - run of pg_upgrade for new instance [05:40:22.761](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 22313 [05:40:22.885](0.124s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=50599 host=/tmp/2N22PCd97z dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_g3Le/dump2.sql [05:40:25.067](2.182s) ok 17 - dump after running pg_upgrade [05:40:25.151](0.083s) ok 18 - old and new dumps match after pg_upgrade [05:40:25.151](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:40:25.257](0.106s) # Looks like you failed 1 test of 18.