[10:39:33.990](0.012s) # testing using transfer mode --link # Checking port 57139 # Found port 57139 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=57139 host=/tmp/4gjRo1F_UM Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [10:39:34.048](0.058s) # 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 6084 [10:39:36.208](2.160s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [10:39:36.262](0.055s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [10:39:36.340](0.078s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [10:39:36.401](0.061s) ok 4 - created database with ASCII characters from 91 to 127 [10:39:36.403](0.002s) # running regression tests in old instance # using postmaster on /tmp/4gjRo1F_UM, port 57139 ok 1 - test_setup 362 ms # parallel group (20 tests): char varchar pg_lsn oid name txid int2 text uuid money int4 regproc boolean float4 int8 float8 enum bit rangetypes numeric ok 2 + boolean 308 ms ok 3 + char 125 ms ok 4 + name 168 ms ok 5 + varchar 132 ms ok 6 + text 228 ms ok 7 + int2 221 ms ok 8 + int4 273 ms ok 9 + int8 327 ms ok 10 + oid 152 ms ok 11 + float4 308 ms ok 12 + float8 354 ms ok 13 + bit 390 ms ok 14 + numeric 1155 ms ok 15 + txid 176 ms ok 16 + uuid 235 ms ok 17 + enum 385 ms ok 18 + money 268 ms ok 19 + rangetypes 843 ms ok 20 + pg_lsn 146 ms ok 21 + regproc 278 ms # parallel group (20 tests): lseg circle md5 path time point timetz macaddr line macaddr8 numerology polygon inet date box interval timestamp timestamptz strings multirangetypes ok 22 + strings 637 ms ok 23 + md5 94 ms ok 24 + numerology 231 ms ok 25 + point 124 ms ok 26 + lseg 77 ms ok 27 + line 179 ms ok 28 + box 435 ms ok 29 + path 96 ms ok 30 + polygon 290 ms ok 31 + circle 90 ms ok 32 + date 382 ms ok 33 + time 118 ms ok 34 + timetz 129 ms ok 35 + timestamp 556 ms ok 36 + timestamptz 613 ms ok 37 + interval 492 ms ok 38 + inet 289 ms ok 39 + macaddr 130 ms ok 40 + macaddr8 191 ms ok 41 + multirangetypes 841 ms # parallel group (12 tests): comments unicode mvcc misc_sanity xid tstypes type_sanity expressions horology geometry regex opr_sanity ok 42 + geometry 351 ms ok 43 + horology 348 ms ok 44 + tstypes 204 ms ok 45 + regex 352 ms ok 46 + type_sanity 316 ms ok 47 + opr_sanity 497 ms ok 48 + misc_sanity 105 ms ok 49 + comments 31 ms ok 50 + expressions 322 ms ok 51 + unicode 50 ms ok 52 + xid 143 ms ok 53 + mvcc 88 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 364 ms ok 55 + copyselect 61 ms ok 56 + copydml 120 ms ok 57 + insert 1174 ms ok 58 + insert_conflict 797 ms # parallel group (7 tests): create_function_c create_misc create_schema create_type create_operator create_procedure create_table ok 59 + create_function_c 28 ms ok 60 + create_misc 184 ms ok 61 + create_operator 214 ms ok 62 + create_procedure 217 ms ok 63 + create_table 1321 ms ok 64 + create_type 201 ms ok 65 + create_schema 187 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2322 ms ok 67 + create_index_spgist 1112 ms ok 68 + create_view 1577 ms ok 69 + index_including 795 ms ok 70 + index_including_gist 561 ms # parallel group (16 tests): create_cast hash_func errors select roleattributes create_aggregate drop_if_exists create_am typed_table infinite_recurse create_function_sql vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 298 ms ok 72 + create_function_sql 492 ms ok 73 + create_cast 123 ms ok 74 + constraints 1765 ms ok 75 + triggers 4575 ms ok 76 + select 225 ms ok 77 + inherit 4047 ms ok 78 + typed_table 438 ms ok 79 + vacuum 1072 ms ok 80 + drop_if_exists 352 ms ok 81 + updatable_views 2931 ms ok 82 + roleattributes 280 ms ok 83 + create_am 364 ms ok 84 + hash_func 158 ms ok 85 + errors 168 ms ok 86 + infinite_recurse 484 ms ok 87 - sanity_check 110 ms # parallel group (20 tests): select_distinct_on delete select_having namespace select_implicit random case select_into select_distinct prepared_xacts union portals arrays subselect transactions hash_index aggregates update btree_index join ok 88 + select_into 297 ms ok 89 + select_distinct 319 ms ok 90 + select_distinct_on 89 ms ok 91 + select_implicit 225 ms ok 92 + select_having 140 ms ok 93 + subselect 731 ms ok 94 + union 560 ms ok 95 + case 250 ms ok 96 + join 3253 ms ok 97 + aggregates 1809 ms ok 98 + transactions 759 ms ok 99 + random 226 ms ok 100 + portals 643 ms ok 101 + arrays 716 ms ok 102 + btree_index 2711 ms ok 103 + hash_index 944 ms ok 104 + update 2194 ms ok 105 + delete 99 ms ok 106 + namespace 196 ms ok 107 + prepared_xacts 338 ms # parallel group (20 tests): init_privs tablesample drop_operator security_label password lock object_address groupingsets spgist collate replica_identity gin gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 4120 ms ok 109 + gin 1670 ms ok 110 + gist 1817 ms ok 111 + spgist 1191 ms ok 112 + privileges 4750 ms ok 113 + init_privs 77 ms ok 114 + security_label 473 ms ok 115 + collate 1489 ms ok 116 + matview 2198 ms ok 117 + lock 908 ms ok 118 + replica_identity 1507 ms ok 119 + rowsecurity 4649 ms ok 120 + object_address 930 ms ok 121 + tablesample 327 ms ok 122 + groupingsets 1048 ms ok 123 + drop_operator 341 ms ok 124 + password 499 ms ok 125 + identity 2440 ms ok 126 + generated 3312 ms ok 127 + join_hash 4148 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 171 ms ok 129 + brin_multi 866 ms # parallel group (18 tests): async dbsize collate.utf8 sysviews tidscan tidrangescan tid misc alter_operator tsrf incremental_sort create_role misc_functions alter_generic create_table_like collate.icu.utf8 merge without_overlaps ok 130 + create_table_like 1548 ms ok 131 + alter_generic 1155 ms ok 132 + alter_operator 488 ms ok 133 + misc 418 ms ok 134 + async 125 ms ok 135 + dbsize 157 ms ok 136 + merge 1838 ms ok 137 + misc_functions 763 ms ok 138 + sysviews 287 ms ok 139 + tsrf 494 ms ok 140 + tid 354 ms ok 141 + tidscan 324 ms ok 142 + tidrangescan 336 ms ok 143 + collate.utf8 187 ms ok 144 + collate.icu.utf8 1666 ms ok 145 + incremental_sort 585 ms ok 146 + create_role 754 ms ok 147 + without_overlaps 2616 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1828 ms ok 149 + psql 1514 ms ok 150 + psql_crosstab 76 ms ok 151 + amutils 33 ms ok 152 + stats_ext 3291 ms ok 153 + collate.linux.utf8 15 ms ok 154 + collate.windows.win1252 21 ms ok 155 - select_parallel 1201 ms ok 156 - write_parallel 156 ms ok 157 - vacuum_parallel 97 ms # parallel group (2 tests): subscription publication ok 158 + publication 2428 ms ok 159 + subscription 158 ms # parallel group (17 tests): portals_p2 advisory_lock combocid xmlmap dependency functional_deps bitmapops tsdicts select_views indirect_toast equivclass guc window cluster tsearch foreign_data foreign_key ok 160 + select_views 621 ms ok 161 + portals_p2 103 ms ok 162 + foreign_key 7123 ms ok 163 + cluster 1478 ms ok 164 + dependency 502 ms ok 165 + guc 733 ms ok 166 + bitmapops 534 ms ok 167 + combocid 209 ms ok 168 + tsearch 1487 ms ok 169 + tsdicts 583 ms ok 170 + foreign_data 3014 ms ok 171 + window 1078 ms ok 172 + xmlmap 333 ms ok 173 + functional_deps 527 ms ok 174 + advisory_lock 169 ms ok 175 + indirect_toast 664 ms ok 176 + equivclass 684 ms # parallel group (9 tests): json_encoding jsonpath_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 520 ms ok 178 + jsonb 777 ms ok 179 + json_encoding 65 ms ok 180 + jsonpath 298 ms ok 181 + jsonpath_encoding 207 ms ok 182 + jsonb_jsonpath 525 ms ok 183 + sqljson 365 ms ok 184 + sqljson_queryfuncs 418 ms ok 185 + sqljson_jsontable 261 ms # parallel group (18 tests): prepare returning conversion limit plancache temp rowtypes sequence truncate with copy2 largeobject polymorphism xml rangefuncs domain plpgsql alter_table ok 186 + plancache 515 ms ok 187 + limit 514 ms ok 188 + plpgsql 3235 ms ok 189 + copy2 1168 ms ok 190 + temp 704 ms ok 191 + domain 1583 ms ok 192 + rangefuncs 1449 ms ok 193 + prepare 181 ms ok 194 + conversion 407 ms ok 195 + truncate 1072 ms ok 196 + alter_table 10614 ms ok 197 + sequence 992 ms ok 198 + polymorphism 1225 ms ok 199 + rowtypes 935 ms ok 200 + returning 300 ms ok 201 + largeobject 1203 ms ok 202 + with 1099 ms ok 203 + xml 1376 ms # parallel group (15 tests): predicate hash_part partition_info reloptions explain memoize compression partition_merge partition_aggregate stats tuplesort partition_split partition_prune partition_join indexing ok 204 + partition_merge 1481 ms ok 205 + partition_split 2841 ms ok 206 + partition_join 4455 ms ok 207 + partition_prune 4177 ms ok 208 + reloptions 129 ms ok 209 + hash_part 115 ms ok 210 + indexing 4989 ms ok 211 + partition_aggregate 1662 ms ok 212 + partition_info 116 ms ok 213 + tuplesort 2254 ms ok 214 + explain 325 ms ok 215 + compression 1320 ms ok 216 + memoize 516 ms ok 217 + stats 2126 ms ok 218 + predicate 76 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 796 ms ok 220 + event_trigger 929 ms ok 221 - event_trigger_login 59 ms ok 222 - fast_default 489 ms ok 223 - tablespace 1425 ms 1..223 # All 223 tests passed. [10:40:34.842](58.439s) ok 5 - regression tests pass # Checking port 57140 # Found port 57140 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=57140 host=/tmp/4gjRo1F_UM Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [10:40:34.845](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=57139 host=/tmp/4gjRo1F_UM dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_CJbc/dump1.sql [10:40:40.120](5.275s) 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/4gjRo1F_UM -p 57139 -P 57140 --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 [10:40:40.288](0.168s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [10:40:40.288](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/4gjRo1F_UM -p 57139 -P 57140 --link --check [10:40:40.870](0.582s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [10:40:40.871](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [10:40:40.871](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 18632 ### 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/4gjRo1F_UM -p 57139 -P 57140 --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* [10:40:43.075](2.204s) ok 12 - run of pg_upgrade --check for new instance [10:40:43.091](0.016s) 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/4gjRo1F_UM -p 57139 -P 57140 --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 [10:41:04.218](21.127s) ok 14 - run of pg_upgrade for new instance [10:41:04.218](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 22673 [10:41:04.341](0.123s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=57140 host=/tmp/4gjRo1F_UM dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_CJbc/dump2.sql [10:41:06.717](2.376s) ok 17 - dump after running pg_upgrade [10:41:06.795](0.078s) ok 18 - old and new dumps match after pg_upgrade # Checking port 57141 # Found port 57141 Name: dst_node Data directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_dst_node_data/pgdata Backup directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_dst_node_data/backup Archive directory: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_dst_node_data/archives Connection string: port=57141 host=/tmp/4gjRo1F_UM Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_dst_node.log [10:41:06.799](0.004s) # initializing database system by copying initdb template # Running: cp -RPp /tmp/cirrus-ci-build/build/tmp_install/initdb-template /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_dst_node_data/pgdata # 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_dst_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.... stopped waiting pg_ctl: could not start server Examine the log output. # pg_ctl start failed; see logfile for details: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log # No postmaster PID for node "old_node" [10:41:06.974](0.175s) Bail out! pg_ctl start failed # No postmaster PID for node "old_node" # Postmaster PID for node "new_node" is 22673 ### 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" # No postmaster PID for node "dst_node"