[13:35:26.804](0.013s) # testing using transfer mode --link # Checking port 65013 # Found port 65013 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=65013 host=/tmp/wGgXZqIYwt Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [13:35:26.813](0.009s) # 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 6039 [13:35:28.872](2.059s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [13:35:28.988](0.117s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [13:35:29.107](0.118s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [13:35:29.173](0.066s) ok 4 - created database with ASCII characters from 91 to 127 [13:35:29.176](0.003s) # running regression tests in old instance # using postmaster on /tmp/wGgXZqIYwt, port 65013 ok 1 - test_setup 436 ms # parallel group (20 tests): varchar pg_lsn char oid txid name uuid text int4 int2 money boolean regproc float4 bit int8 float8 enum rangetypes numeric ok 2 + boolean 253 ms ok 3 + char 138 ms ok 4 + name 182 ms ok 5 + varchar 131 ms ok 6 + text 215 ms ok 7 + int2 237 ms ok 8 + int4 232 ms ok 9 + int8 305 ms ok 10 + oid 158 ms ok 11 + float4 278 ms ok 12 + float8 336 ms ok 13 + bit 297 ms ok 14 + numeric 922 ms ok 15 + txid 176 ms ok 16 + uuid 188 ms ok 17 + enum 336 ms ok 18 + money 246 ms ok 19 + rangetypes 839 ms ok 20 + pg_lsn 136 ms ok 21 + regproc 252 ms # parallel group (20 tests): md5 circle lseg path point line time timetz macaddr macaddr8 inet numerology polygon date box strings timestamp interval timestamptz multirangetypes ok 22 + strings 603 ms ok 23 + md5 47 ms ok 24 + numerology 224 ms ok 25 + point 120 ms ok 26 + lseg 75 ms ok 27 + line 120 ms ok 28 + box 380 ms ok 29 + path 81 ms ok 30 + polygon 296 ms ok 31 + circle 74 ms ok 32 + date 296 ms ok 33 + time 142 ms ok 34 + timetz 148 ms ok 35 + timestamp 629 ms ok 36 + timestamptz 690 ms ok 37 + interval 634 ms ok 38 + inet 217 ms ok 39 + macaddr 149 ms ok 40 + macaddr8 177 ms ok 41 + multirangetypes 902 ms # parallel group (12 tests): comments misc_sanity mvcc unicode xid expressions type_sanity geometry tstypes regex horology opr_sanity ok 42 + geometry 325 ms ok 43 + horology 407 ms ok 44 + tstypes 353 ms ok 45 + regex 357 ms ok 46 + type_sanity 241 ms ok 47 + opr_sanity 497 ms ok 48 + misc_sanity 42 ms ok 49 + comments 37 ms ok 50 + expressions 212 ms ok 51 + unicode 102 ms ok 52 + xid 199 ms ok 53 + mvcc 100 ms # parallel group (5 tests): copyselect copydml copy insert_conflict insert ok 54 + copy 275 ms ok 55 + copyselect 142 ms ok 56 + copydml 154 ms ok 57 + insert 1094 ms ok 58 + insert_conflict 607 ms # parallel group (7 tests): create_function_c create_operator create_schema create_type create_misc create_procedure create_table ok 59 + create_function_c 20 ms ok 60 + create_misc 140 ms ok 61 + create_operator 102 ms ok 62 + create_procedure 157 ms ok 63 + create_table 1516 ms ok 64 + create_type 129 ms ok 65 + create_schema 120 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2227 ms ok 67 + create_index_spgist 1028 ms ok 68 + create_view 1410 ms ok 69 + index_including 776 ms ok 70 + index_including_gist 603 ms # parallel group (16 tests): errors roleattributes hash_func create_cast create_aggregate select infinite_recurse typed_table drop_if_exists create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 339 ms ok 72 + create_function_sql 552 ms ok 73 + create_cast 242 ms ok 74 + constraints 1911 ms ok 75 + triggers 6136 ms ok 76 + select 350 ms ok 77 + inherit 4108 ms ok 78 + typed_table 446 ms ok 79 + vacuum 924 ms ok 80 + drop_if_exists 462 ms ok 81 + updatable_views 3484 ms ok 82 + roleattributes 127 ms ok 83 + create_am 603 ms ok 84 + hash_func 229 ms ok 85 + errors 64 ms ok 86 + infinite_recurse 390 ms ok 87 - sanity_check 121 ms # parallel group (20 tests): select_distinct_on delete select_having namespace random select_implicit select_into case select_distinct prepared_xacts union transactions subselect portals hash_index arrays update aggregates btree_index join ok 88 + select_into 317 ms ok 89 + select_distinct 343 ms ok 90 + select_distinct_on 67 ms ok 91 + select_implicit 272 ms ok 92 + select_having 161 ms ok 93 + subselect 943 ms ok 94 + union 754 ms ok 95 + case 326 ms ok 96 + join 1950 ms ok 97 + aggregates 1737 ms ok 98 + transactions 941 ms ok 99 + random 237 ms ok 100 + portals 957 ms ok 101 + arrays 1098 ms ok 102 + btree_index 1892 ms ok 103 + hash_index 971 ms ok 104 + update 1452 ms ok 105 + delete 108 ms ok 106 + namespace 210 ms ok 107 + prepared_xacts 404 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock groupingsets object_address collate replica_identity spgist gin gist matview identity generated brin join_hash rowsecurity privileges ok 108 + brin 3907 ms ok 109 + gin 1525 ms ok 110 + gist 1632 ms ok 111 + spgist 1315 ms ok 112 + privileges 4552 ms ok 113 + init_privs 66 ms ok 114 + security_label 319 ms ok 115 + collate 1212 ms ok 116 + matview 2632 ms ok 117 + lock 1011 ms ok 118 + replica_identity 1273 ms ok 119 + rowsecurity 4548 ms ok 120 + object_address 1152 ms ok 121 + tablesample 324 ms ok 122 + groupingsets 1055 ms ok 123 + drop_operator 136 ms ok 124 + password 792 ms ok 125 + identity 2721 ms ok 126 + generated 3800 ms ok 127 + join_hash 3917 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 134 ms ok 129 + brin_multi 827 ms # parallel group (18 tests): async dbsize collate.utf8 sysviews tidscan tidrangescan tid tsrf alter_operator misc create_role misc_functions incremental_sort alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 1095 ms ok 131 + alter_generic 706 ms ok 132 + alter_operator 338 ms ok 133 + misc 351 ms ok 134 + async 67 ms ok 135 + dbsize 94 ms ok 136 + merge 1112 ms ok 137 + misc_functions 430 ms ok 138 + sysviews 151 ms ok 139 + tsrf 312 ms ok 140 + tid 282 ms ok 141 + tidscan 226 ms ok 142 + tidrangescan 247 ms ok 143 + collate.utf8 145 ms ok 144 + collate.icu.utf8 1079 ms ok 145 + incremental_sort 437 ms ok 146 + create_role 375 ms ok 147 + without_overlaps 1476 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 2011 ms ok 149 + psql 1638 ms ok 150 + psql_crosstab 107 ms ok 151 + amutils 82 ms ok 152 + stats_ext 3835 ms ok 153 + collate.linux.utf8 60 ms ok 154 + collate.windows.win1252 60 ms ok 155 - select_parallel 2523 ms ok 156 - write_parallel 154 ms ok 157 - vacuum_parallel 123 ms # parallel group (2 tests): subscription publication ok 158 + publication 1341 ms ok 159 + subscription 108 ms # parallel group (17 tests): advisory_lock portals_p2 combocid xmlmap bitmapops dependency functional_deps tsdicts guc select_views equivclass indirect_toast cluster tsearch window foreign_data foreign_key ok 160 + select_views 491 ms ok 161 + portals_p2 160 ms ok 162 + foreign_key 7366 ms ok 163 + cluster 857 ms ok 164 + dependency 389 ms ok 165 + guc 490 ms ok 166 + bitmapops 302 ms ok 167 + combocid 265 ms ok 168 + tsearch 940 ms ok 169 + tsdicts 451 ms ok 170 + foreign_data 2904 ms ok 171 + window 990 ms ok 172 + xmlmap 297 ms ok 173 + functional_deps 389 ms ok 174 + advisory_lock 141 ms ok 175 + indirect_toast 589 ms ok 176 + equivclass 558 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 353 ms ok 178 + jsonb 766 ms ok 179 + json_encoding 82 ms ok 180 + jsonpath 221 ms ok 181 + jsonpath_encoding 77 ms ok 182 + jsonb_jsonpath 456 ms ok 183 + sqljson 254 ms ok 184 + sqljson_queryfuncs 315 ms ok 185 + sqljson_jsontable 192 ms # parallel group (18 tests): prepare conversion limit returning plancache temp rowtypes copy2 truncate sequence with largeobject xml polymorphism rangefuncs domain plpgsql alter_table ok 186 + plancache 550 ms ok 187 + limit 401 ms ok 188 + plpgsql 2491 ms ok 189 + copy2 973 ms ok 190 + temp 791 ms ok 191 + domain 1490 ms ok 192 + rangefuncs 1292 ms ok 193 + prepare 127 ms ok 194 + conversion 381 ms ok 195 + truncate 1130 ms ok 196 + alter_table 12329 ms ok 197 + sequence 1131 ms ok 198 + polymorphism 1234 ms ok 199 + rowtypes 920 ms ok 200 + returning 418 ms ok 201 + largeobject 1160 ms ok 202 + with 1154 ms ok 203 + xml 1194 ms # parallel group (15 tests): hash_part predicate reloptions explain memoize partition_info compression partition_merge partition_aggregate stats tuplesort partition_split partition_join partition_prune indexing ok 204 + partition_merge 1320 ms ok 205 + partition_split 2100 ms ok 206 + partition_join 4229 ms ok 207 + partition_prune 4436 ms ok 208 + reloptions 203 ms ok 209 + hash_part 100 ms ok 210 + indexing 5229 ms ok 211 + partition_aggregate 1421 ms ok 212 + partition_info 334 ms ok 213 + tuplesort 1654 ms ok 214 + explain 197 ms ok 215 + compression 1166 ms ok 216 + memoize 307 ms ok 217 + stats 1627 ms ok 218 + predicate 154 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 537 ms ok 220 + event_trigger 638 ms ok 221 - event_trigger_login 84 ms ok 222 - fast_default 424 ms ok 223 - tablespace 1198 ms 1..223 # All 223 tests passed. [13:36:28.742](59.566s) ok 5 - regression tests pass # Checking port 65014 # Found port 65014 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=65014 host=/tmp/wGgXZqIYwt Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [13:36:28.745](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=65013 host=/tmp/wGgXZqIYwt dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_Puhs/dump1.sql [13:36:32.706](3.961s) 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/wGgXZqIYwt -p 65013 -P 65014 --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 [13:36:32.924](0.218s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [13:36:32.925](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/wGgXZqIYwt -p 65013 -P 65014 --link --check [13:36:34.256](1.331s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [13:36:34.256](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [13:36:34.256](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 18964 ### 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/wGgXZqIYwt -p 65013 -P 65014 --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* [13:36:36.734](2.477s) ok 12 - run of pg_upgrade --check for new instance [13:36:36.734](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/wGgXZqIYwt -p 65013 -P 65014 --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 [13:36:54.416](17.682s) ok 14 - run of pg_upgrade for new instance [13:36:54.416](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 22675 [13:36:54.545](0.129s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=65014 host=/tmp/wGgXZqIYwt dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_Puhs/dump2.sql [13:36:56.700](2.155s) ok 17 - dump after running pg_upgrade [13:36:56.837](0.138s) ok 18 - old and new dumps match after pg_upgrade # Checking port 65015 # Found port 65015 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=65015 host=/tmp/wGgXZqIYwt Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_dst_node.log [13:36:56.843](0.006s) # 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" [13:36:57.024](0.180s) Bail out! pg_ctl start failed # No postmaster PID for node "old_node" # Postmaster PID for node "new_node" is 22675 ### 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"