[06:06:40.707](0.013s) # testing using transfer mode --link # Checking port 63186 # Found port 63186 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=63186 host=/tmp/y3hIrgv5Wh Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [06:06:40.712](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 --locale C --locale-provider icu --icu-locale fr-CA The files belonging to this database system will be owned by user "postgres". This user must also own the server process. Using language tag "fr-CA" for ICU locale "fr-CA". The database cluster will be initialized with this locale configuration: provider: icu ICU locale: fr-CA LC_COLLATE: C LC_CTYPE: C LC_MESSAGES: C LC_MONETARY: C LC_NUMERIC: C LC_TIME: C 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 7289 [06:06:42.262](1.549s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [06:06:42.296](0.035s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [06:06:42.331](0.035s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [06:06:42.365](0.034s) ok 4 - created database with ASCII characters from 91 to 127 [06:06:42.366](0.000s) # running regression tests in old instance # using postmaster on /tmp/y3hIrgv5Wh, port 63186 ok 1 - test_setup 432 ms # parallel group (20 tests): varchar txid oid name char pg_lsn int2 uuid text int4 regproc boolean float4 money int8 bit float8 enum rangetypes numeric ok 2 + boolean 154 ms ok 3 + char 97 ms ok 4 + name 84 ms ok 5 + varchar 73 ms ok 6 + text 140 ms ok 7 + int2 112 ms ok 8 + int4 144 ms ok 9 + int8 183 ms ok 10 + oid 81 ms ok 11 + float4 161 ms ok 12 + float8 205 ms ok 13 + bit 200 ms ok 14 + numeric 576 ms ok 15 + txid 73 ms ok 16 + uuid 118 ms ok 17 + enum 210 ms ok 18 + money 165 ms ok 19 + rangetypes 450 ms ok 20 + pg_lsn 96 ms ok 21 + regproc 148 ms # parallel group (20 tests): md5 lseg path circle macaddr line timetz point time inet numerology macaddr8 polygon date interval box strings multirangetypes timestamp timestamptz ok 22 + strings 349 ms ok 23 + md5 55 ms ok 24 + numerology 158 ms ok 25 + point 94 ms ok 26 + lseg 62 ms ok 27 + line 90 ms ok 28 + box 298 ms ok 29 + path 64 ms ok 30 + polygon 187 ms ok 31 + circle 74 ms ok 32 + date 197 ms ok 33 + time 105 ms ok 34 + timetz 90 ms ok 35 + timestamp 403 ms ok 36 + timestamptz 443 ms ok 37 + interval 227 ms ok 38 + inet 148 ms ok 39 + macaddr 86 ms ok 40 + macaddr8 170 ms ok 41 + multirangetypes 389 ms # parallel group (12 tests): comments misc_sanity unicode mvcc type_sanity expressions xid geometry tstypes horology regex opr_sanity ok 42 + geometry 180 ms ok 43 + horology 252 ms ok 44 + tstypes 234 ms ok 45 + regex 280 ms ok 46 + type_sanity 131 ms ok 47 + opr_sanity 330 ms ok 48 + misc_sanity 28 ms ok 49 + comments 24 ms ok 50 + expressions 133 ms ok 51 + unicode 48 ms ok 52 + xid 171 ms ok 53 + mvcc 59 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 360 ms ok 55 + copyselect 68 ms ok 56 + copydml 294 ms ok 57 + insert 848 ms ok 58 + insert_conflict 543 ms # parallel group (7 tests): create_function_c create_misc create_type create_procedure create_operator create_schema create_table ok 59 + create_function_c 28 ms ok 60 + create_misc 69 ms ok 61 + create_operator 95 ms ok 62 + create_procedure 91 ms ok 63 + create_table 1069 ms ok 64 + create_type 88 ms ok 65 + create_schema 98 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 1229 ms ok 67 + create_index_spgist 767 ms ok 68 + create_view 786 ms ok 69 + index_including 459 ms ok 70 + index_including_gist 406 ms # parallel group (16 tests): create_cast errors roleattributes create_aggregate hash_func select create_function_sql typed_table infinite_recurse create_am drop_if_exists vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 110 ms ok 72 + create_function_sql 288 ms ok 73 + create_cast 51 ms ok 74 + constraints 989 ms ok 75 + triggers 2903 ms ok 76 + select 218 ms ok 77 + inherit 2770 ms ok 78 + typed_table 304 ms ok 79 + vacuum 602 ms ok 80 + drop_if_exists 408 ms ok 81 + updatable_views 2377 ms ok 82 + roleattributes 69 ms ok 83 + create_am 346 ms ok 84 + hash_func 153 ms ok 85 + errors 51 ms ok 86 + infinite_recurse 336 ms ok 87 - sanity_check 104 ms # parallel group (20 tests): select_distinct_on random delete select_having select_implicit namespace case select_into select_distinct prepared_xacts union transactions portals subselect arrays hash_index update aggregates btree_index join ok 88 + select_into 416 ms ok 89 + select_distinct 522 ms ok 90 + select_distinct_on 77 ms ok 91 + select_implicit 150 ms ok 92 + select_having 130 ms ok 93 + subselect 1650 ms ok 94 + union 928 ms ok 95 + case 194 ms ok 96 + join 2705 ms ok 97 + aggregates 2414 ms ok 98 + transactions 999 ms ok 99 + random 94 ms ok 100 + portals 1128 ms ok 101 + arrays 1662 ms ok 102 + btree_index 2463 ms ok 103 + hash_index 1797 ms ok 104 + update 2070 ms ok 105 + delete 111 ms ok 106 + namespace 176 ms ok 107 + prepared_xacts 543 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password object_address lock replica_identity groupingsets spgist collate gist gin identity matview privileges generated rowsecurity brin join_hash ok 108 + brin 2821 ms ok 109 + gin 1389 ms ok 110 + gist 1366 ms ok 111 + spgist 905 ms ok 112 + privileges 2173 ms ok 113 + init_privs 46 ms ok 114 + security_label 222 ms ok 115 + collate 1201 ms ok 116 + matview 1845 ms ok 117 + lock 510 ms ok 118 + replica_identity 892 ms ok 119 + rowsecurity 2759 ms ok 120 + object_address 376 ms ok 121 + tablesample 337 ms ok 122 + groupingsets 904 ms ok 123 + drop_operator 87 ms ok 124 + password 357 ms ok 125 + identity 1829 ms ok 126 + generated 2698 ms ok 127 + join_hash 2819 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 115 ms ok 129 + brin_multi 612 ms # parallel group (17 tests): async sysviews dbsize tidscan tidrangescan alter_operator tsrf misc tid misc_functions create_role incremental_sort alter_generic without_overlaps merge collate.icu.utf8 create_table_like ok 130 + create_table_like 727 ms ok 131 + alter_generic 401 ms ok 132 + alter_operator 164 ms ok 133 + misc 212 ms ok 134 + async 62 ms ok 135 + dbsize 108 ms ok 136 + merge 609 ms ok 137 + misc_functions 232 ms ok 138 + sysviews 78 ms ok 139 + tsrf 192 ms ok 140 + tid 228 ms ok 141 + tidscan 129 ms ok 142 + tidrangescan 145 ms ok 143 + collate.icu.utf8 682 ms ok 144 + incremental_sort 366 ms ok 145 + create_role 271 ms ok 146 + without_overlaps 463 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 147 + rules 819 ms ok 148 + psql 849 ms ok 149 + psql_crosstab 43 ms ok 150 + amutils 25 ms ok 151 + stats_ext 1492 ms ok 152 + collate.linux.utf8 18 ms ok 153 + collate.windows.win1252 13 ms ok 154 - select_parallel 612 ms ok 155 - write_parallel 385 ms ok 156 - vacuum_parallel 149 ms # parallel group (2 tests): subscription publication ok 157 + publication 695 ms ok 158 + subscription 97 ms # parallel group (17 tests): advisory_lock portals_p2 combocid xmlmap bitmapops functional_deps tsdicts select_views dependency guc equivclass indirect_toast window tsearch cluster foreign_data foreign_key ok 159 + select_views 340 ms ok 160 + portals_p2 137 ms ok 161 + foreign_key 3142 ms ok 162 + cluster 766 ms ok 163 + dependency 365 ms ok 164 + guc 365 ms ok 165 + bitmapops 277 ms ok 166 + combocid 242 ms ok 167 + tsearch 690 ms ok 168 + tsdicts 339 ms ok 169 + foreign_data 1282 ms ok 170 + window 684 ms ok 171 + xmlmap 249 ms ok 172 + functional_deps 295 ms ok 173 + advisory_lock 78 ms ok 174 + indirect_toast 426 ms ok 175 + equivclass 373 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 241 ms ok 177 + jsonb 429 ms ok 178 + json_encoding 28 ms ok 179 + jsonpath 60 ms ok 180 + jsonpath_encoding 15 ms ok 181 + jsonb_jsonpath 299 ms ok 182 + sqljson 103 ms # parallel group (18 tests): prepare limit plancache returning conversion temp truncate with sequence rowtypes copy2 polymorphism largeobject xml domain rangefuncs plpgsql alter_table ok 183 + plancache 338 ms ok 184 + limit 305 ms ok 185 + plpgsql 1581 ms ok 186 + copy2 728 ms ok 187 + temp 512 ms ok 188 + domain 958 ms ok 189 + rangefuncs 961 ms ok 190 + prepare 149 ms ok 191 + conversion 366 ms ok 192 + truncate 622 ms ok 193 + alter_table 3569 ms ok 194 + sequence 674 ms ok 195 + polymorphism 792 ms ok 196 + rowtypes 707 ms ok 197 + returning 336 ms ok 198 + largeobject 823 ms ok 199 + with 643 ms ok 200 + xml 900 ms # parallel group (13 tests): predicate hash_part partition_info explain reloptions memoize compression partition_aggregate tuplesort stats partition_join partition_prune indexing ok 201 + partition_join 1542 ms ok 202 + partition_prune 1570 ms ok 203 + reloptions 218 ms ok 204 + hash_part 70 ms ok 205 + indexing 1734 ms ok 206 + partition_aggregate 938 ms ok 207 + partition_info 207 ms ok 208 + tuplesort 999 ms not ok 209 + explain 214 ms ok 210 + compression 652 ms ok 211 + memoize 317 ms ok 212 + stats 1096 ms ok 213 + predicate 45 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 229 ms ok 215 + event_trigger 273 ms ok 216 - event_trigger_login 26 ms ok 217 - fast_default 250 ms ok 218 - tablespace 693 ms 1..218 # 1 of 218 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/explain.out /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/explain.out --- /tmp/cirrus-ci-build/src/test/regress/expected/explain.out 2024-03-11 06:04:50.658180000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/explain.out 2024-03-11 06:07:08.278570000 +0000 @@ -332,16 +332,16 @@ CONTEXT: PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement -- MEMORY option select explain_filter('explain (memory) select * from int8_tbl i8'); - explain_filter ---------------------------------------------------------- - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) + explain_filter +----------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) Memory: used=N bytes allocated=N bytes (2 rows) select explain_filter('explain (memory, analyze) select * from int8_tbl i8'); - explain_filter ------------------------------------------------------------------------------------------------ - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) (actual time=N.N..N.N rows=N loops=N) + explain_filter +------------------------------------------------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) (actual time=N.N..N.N rows=N loops=N) Memory: used=N bytes allocated=N bytes Planning Time: N.N ms Execution Time: N.N ms @@ -360,6 +360,7 @@ Total Cost: N.N + Plan Rows: N + Plan Width: N + + Plan Calls: N + Planning: + Memory Used: N + Memory Allocated: N + @@ -381,6 +382,7 @@ "Total Cost": N.N, + "Plan Rows": N, + "Plan Width": N, + + "Plan Calls": N, + "Actual Startup Time": N.N, + "Actual Total Time": N.N, + "Actual Rows": N, + @@ -400,9 +402,9 @@ prepare int8_query as select * from int8_tbl i8; select explain_filter('explain (memory) execute int8_query'); - explain_filter ---------------------------------------------------------- - Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N) + explain_filter +----------------------------------------------------------------- + Seq Scan on int8_tbl i8 (cost=N.N..N.N rows=N width=N loops=N) Memory: used=N bytes allocated=N bytes (2 rows) === EOF === [06:07:11.084](28.719s) not ok 5 - regression tests pass [06:07:11.085](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 223. [06:07:11.085](0.000s) # got: '256' # expected: '0' # Checking port 63187 # Found port 63187 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=63187 host=/tmp/y3hIrgv5Wh Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [06:07:11.087](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: 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=63186 host=/tmp/y3hIrgv5Wh dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TOyf/dump1.sql [06:07:13.796](2.708s) 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/y3hIrgv5Wh -p 63186 -P 63187 --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:07:13.940](0.144s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [06:07:13.940](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/y3hIrgv5Wh -p 63186 -P 63187 --link --check [06:07:14.352](0.412s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [06:07:14.352](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [06:07:14.353](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 10774 ### 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/y3hIrgv5Wh -p 63186 -P 63187 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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:07:15.757](1.404s) ok 12 - run of pg_upgrade --check for new instance [06:07:15.757](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/y3hIrgv5Wh -p 63186 -P 63187 --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 system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Checking for valid logical replication slots ok Checking for subscription state 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:07:26.116](10.359s) ok 14 - run of pg_upgrade for new instance [06:07:26.116](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 11811 [06:07:26.238](0.122s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=63187 host=/tmp/y3hIrgv5Wh dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TOyf/dump2.sql [06:07:27.906](1.668s) ok 17 - dump after running pg_upgrade [06:07:27.984](0.078s) ok 18 - old and new dumps match after pg_upgrade [06:07:27.984](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:07:28.095](0.111s) # Looks like you failed 1 test of 18.