[19:32:13.947](0.012s) # testing using transfer mode --link # Checking port 59322 # Found port 59322 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=59322 host=/tmp/mD29TErcmI Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [19:32:13.951](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 7340 [19:32:15.483](1.531s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [19:32:15.516](0.034s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [19:32:15.593](0.076s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [19:32:15.631](0.038s) ok 4 - created database with ASCII characters from 91 to 127 [19:32:15.632](0.000s) # running regression tests in old instance # using postmaster on /tmp/mD29TErcmI, port 59322 ok 1 - test_setup 299 ms # parallel group (20 tests): varchar oid pg_lsn name char txid int2 uuid text regproc money boolean float4 int4 int8 float8 bit enum rangetypes numeric ok 2 + boolean 162 ms ok 3 + char 102 ms ok 4 + name 96 ms ok 5 + varchar 56 ms ok 6 + text 147 ms ok 7 + int2 143 ms ok 8 + int4 178 ms ok 9 + int8 200 ms ok 10 + oid 70 ms ok 11 + float4 170 ms ok 12 + float8 201 ms ok 13 + bit 201 ms ok 14 + numeric 610 ms ok 15 + txid 104 ms ok 16 + uuid 145 ms ok 17 + enum 210 ms ok 18 + money 159 ms ok 19 + rangetypes 500 ms ok 20 + pg_lsn 85 ms ok 21 + regproc 154 ms # parallel group (20 tests): md5 lseg circle macaddr path line time timetz point numerology macaddr8 inet polygon date interval box strings timestamp timestamptz multirangetypes ok 22 + strings 401 ms ok 23 + md5 42 ms ok 24 + numerology 140 ms ok 25 + point 138 ms ok 26 + lseg 46 ms ok 27 + line 71 ms ok 28 + box 386 ms ok 29 + path 68 ms ok 30 + polygon 274 ms ok 31 + circle 63 ms ok 32 + date 287 ms ok 33 + time 101 ms ok 34 + timetz 127 ms ok 35 + timestamp 402 ms ok 36 + timestamptz 457 ms ok 37 + interval 343 ms ok 38 + inet 224 ms ok 39 + macaddr 63 ms ok 40 + macaddr8 147 ms ok 41 + multirangetypes 514 ms # parallel group (12 tests): comments misc_sanity mvcc unicode xid expressions type_sanity tstypes geometry horology regex opr_sanity ok 42 + geometry 193 ms ok 43 + horology 231 ms ok 44 + tstypes 157 ms ok 45 + regex 239 ms ok 46 + type_sanity 131 ms ok 47 + opr_sanity 313 ms ok 48 + misc_sanity 34 ms ok 49 + comments 19 ms ok 50 + expressions 103 ms ok 51 + unicode 48 ms ok 52 + xid 74 ms ok 53 + mvcc 45 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 249 ms ok 55 + copyselect 120 ms ok 56 + copydml 105 ms ok 57 + insert 644 ms ok 58 + insert_conflict 399 ms # parallel group (7 tests): create_function_c create_operator create_procedure create_type create_schema create_misc create_table ok 59 + create_function_c 15 ms ok 60 + create_misc 90 ms ok 61 + create_operator 53 ms ok 62 + create_procedure 71 ms ok 63 + create_table 913 ms ok 64 + create_type 79 ms ok 65 + create_schema 81 ms # parallel group (5 tests): index_including index_including_gist create_index_spgist create_view create_index ok 66 + create_index 1151 ms ok 67 + create_index_spgist 776 ms ok 68 + create_view 784 ms ok 69 + index_including 427 ms ok 70 + index_including_gist 444 ms # parallel group (16 tests): create_aggregate errors select roleattributes create_cast create_am typed_table infinite_recurse hash_func drop_if_exists create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 118 ms ok 72 + create_function_sql 411 ms ok 73 + create_cast 165 ms ok 74 + constraints 709 ms ok 75 + triggers 3012 ms ok 76 + select 137 ms ok 77 + inherit 2726 ms ok 78 + typed_table 296 ms ok 79 + vacuum 591 ms ok 80 + drop_if_exists 362 ms ok 81 + updatable_views 2071 ms ok 82 + roleattributes 143 ms ok 83 + create_am 238 ms ok 84 + hash_func 344 ms ok 85 + errors 130 ms ok 86 + infinite_recurse 343 ms ok 87 - sanity_check 510 ms # parallel group (20 tests): delete random select_distinct_on select_having namespace select_implicit case select_distinct prepared_xacts select_into union transactions subselect portals arrays hash_index update aggregates join btree_index ok 88 + select_into 411 ms ok 89 + select_distinct 349 ms ok 90 + select_distinct_on 166 ms ok 91 + select_implicit 272 ms ok 92 + select_having 195 ms ok 93 + subselect 964 ms ok 94 + union 597 ms ok 95 + case 290 ms ok 96 + join 1731 ms ok 97 + aggregates 1614 ms ok 98 + transactions 784 ms ok 99 + random 153 ms ok 100 + portals 1001 ms ok 101 + arrays 1173 ms ok 102 + btree_index 1768 ms ok 103 + hash_index 1214 ms ok 104 + update 1372 ms ok 105 + delete 139 ms ok 106 + namespace 201 ms ok 107 + prepared_xacts 366 ms # parallel group (20 tests): init_privs drop_operator tablesample security_label object_address lock password collate groupingsets replica_identity spgist gist gin matview identity generated rowsecurity join_hash brin privileges ok 108 + brin 2336 ms ok 109 + gin 1188 ms ok 110 + gist 1146 ms ok 111 + spgist 991 ms ok 112 + privileges 2588 ms ok 113 + init_privs 65 ms ok 114 + security_label 331 ms ok 115 + collate 629 ms ok 116 + matview 1245 ms ok 117 + lock 482 ms ok 118 + replica_identity 858 ms ok 119 + rowsecurity 1756 ms ok 120 + object_address 477 ms ok 121 + tablesample 261 ms ok 122 + groupingsets 697 ms ok 123 + drop_operator 132 ms ok 124 + password 528 ms ok 125 + identity 1478 ms ok 126 + generated 1700 ms ok 127 + join_hash 2329 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 115 ms ok 129 + brin_multi 660 ms # parallel group (17 tests): async dbsize sysviews tidscan alter_operator tidrangescan tid tsrf misc_functions misc incremental_sort create_role without_overlaps alter_generic collate.icu.utf8 merge create_table_like ok 130 + create_table_like 539 ms ok 131 + alter_generic 351 ms ok 132 + alter_operator 146 ms ok 133 + misc 233 ms ok 134 + async 42 ms ok 135 + dbsize 72 ms ok 136 + merge 535 ms ok 137 + misc_functions 214 ms ok 138 + sysviews 101 ms ok 139 + tsrf 185 ms ok 140 + tid 163 ms ok 141 + tidscan 112 ms ok 142 + tidrangescan 152 ms ok 143 + collate.icu.utf8 512 ms ok 144 + incremental_sort 240 ms ok 145 + create_role 242 ms ok 146 + without_overlaps 308 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab rules psql stats_ext ok 147 + rules 660 ms ok 148 + psql 684 ms ok 149 + psql_crosstab 39 ms ok 150 + amutils 32 ms ok 151 + stats_ext 1428 ms ok 152 + collate.linux.utf8 23 ms ok 153 + collate.windows.win1252 16 ms ok 154 - select_parallel 1103 ms ok 155 - write_parallel 80 ms ok 156 - vacuum_parallel 84 ms # parallel group (2 tests): subscription publication ok 157 + publication 602 ms ok 158 + subscription 115 ms # parallel group (17 tests): portals_p2 advisory_lock xmlmap combocid functional_deps equivclass bitmapops dependency guc tsdicts select_views indirect_toast window tsearch cluster foreign_data foreign_key ok 159 + select_views 359 ms ok 160 + portals_p2 78 ms ok 161 + foreign_key 2939 ms ok 162 + cluster 760 ms ok 163 + dependency 330 ms ok 164 + guc 350 ms ok 165 + bitmapops 285 ms ok 166 + combocid 133 ms ok 167 + tsearch 660 ms ok 168 + tsdicts 355 ms ok 169 + foreign_data 1221 ms ok 170 + window 568 ms ok 171 + xmlmap 130 ms ok 172 + functional_deps 208 ms ok 173 + advisory_lock 117 ms ok 174 + indirect_toast 421 ms ok 175 + equivclass 254 ms # parallel group (7 tests): jsonpath_encoding json_encoding jsonpath sqljson json jsonb_jsonpath jsonb ok 176 + json 148 ms ok 177 + jsonb 338 ms ok 178 + json_encoding 38 ms ok 179 + jsonpath 76 ms ok 180 + jsonpath_encoding 26 ms ok 181 + jsonb_jsonpath 203 ms ok 182 + sqljson 109 ms # parallel group (18 tests): returning conversion prepare plancache limit temp with truncate copy2 rowtypes polymorphism sequence largeobject rangefuncs xml domain plpgsql alter_table ok 183 + plancache 309 ms ok 184 + limit 343 ms ok 185 + plpgsql 1418 ms ok 186 + copy2 663 ms ok 187 + temp 419 ms ok 188 + domain 818 ms ok 189 + rangefuncs 799 ms ok 190 + prepare 246 ms ok 191 + conversion 194 ms ok 192 + truncate 642 ms ok 193 + alter_table 3485 ms ok 194 + sequence 770 ms ok 195 + polymorphism 752 ms ok 196 + rowtypes 704 ms ok 197 + returning 179 ms ok 198 + largeobject 785 ms ok 199 + with 625 ms ok 200 + xml 801 ms # parallel group (13 tests): predicate hash_part reloptions explain memoize partition_info compression partition_aggregate tuplesort stats partition_join partition_prune indexing ok 201 + partition_join 1398 ms ok 202 + partition_prune 1407 ms ok 203 + reloptions 138 ms ok 204 + hash_part 117 ms ok 205 + indexing 1613 ms ok 206 + partition_aggregate 903 ms ok 207 + partition_info 290 ms ok 208 + tuplesort 924 ms not ok 209 + explain 178 ms ok 210 + compression 605 ms ok 211 + memoize 220 ms ok 212 + stats 1156 ms ok 213 + predicate 100 ms # parallel group (2 tests): oidjoins event_trigger ok 214 + oidjoins 210 ms ok 215 + event_trigger 246 ms ok 216 - event_trigger_login 24 ms ok 217 - fast_default 223 ms ok 218 - tablespace 680 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-02 19:30:34.912380000 +0000 +++ /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/results/explain.out 2024-03-02 19:32:39.795555000 +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 === [19:32:42.425](26.794s) not ok 5 - regression tests pass [19:32:42.426](0.000s) # Failed test 'regression tests pass' # at /tmp/cirrus-ci-build/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 212. [19:32:42.426](0.000s) # got: '256' # expected: '0' # Checking port 59323 # Found port 59323 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=59323 host=/tmp/mD29TErcmI Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [19:32:42.428](0.002s) # 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=59322 host=/tmp/mD29TErcmI dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_Bqww/dump1.sql [19:32:45.063](2.634s) 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/mD29TErcmI -p 59322 -P 59323 --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 [19:32:45.205](0.142s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [19:32:45.205](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/mD29TErcmI -p 59322 -P 59323 --link --check [19:32:45.613](0.409s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [19:32:45.614](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [19:32:45.614](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 10823 ### 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/mD29TErcmI -p 59322 -P 59323 --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* [19:32:47.017](1.403s) ok 12 - run of pg_upgrade --check for new instance [19:32:47.017](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/mD29TErcmI -p 59322 -P 59323 --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 [19:32:56.360](9.343s) ok 14 - run of pg_upgrade for new instance [19:32:56.360](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 11849 [19:32:56.480](0.121s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=59323 host=/tmp/mD29TErcmI dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_Bqww/dump2.sql [19:32:58.152](1.672s) ok 17 - dump after running pg_upgrade [19:32:58.226](0.073s) ok 18 - old and new dumps match after pg_upgrade [19:32:58.226](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" [19:32:58.330](0.104s) # Looks like you failed 1 test of 18.