[02:35:33.543](0.014s) # testing using transfer mode --link # Checking port 52386 # Found port 52386 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=52386 host=/tmp/6QqOtKAEJG Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [02:35:33.552](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 6059 [02:35:35.562](2.010s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [02:35:35.601](0.039s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [02:35:35.656](0.055s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [02:35:35.706](0.050s) ok 4 - created database with ASCII characters from 91 to 127 [02:35:35.706](0.000s) # running regression tests in old instance # using postmaster on /tmp/6QqOtKAEJG, port 52386 ok 1 - test_setup 467 ms # parallel group (20 tests): varchar char oid txid pg_lsn uuid name text int2 int4 regproc money boolean float4 bit float8 int8 enum rangetypes numeric ok 2 + boolean 344 ms ok 3 + char 155 ms ok 4 + name 241 ms ok 5 + varchar 129 ms ok 6 + text 253 ms ok 7 + int2 256 ms ok 8 + int4 280 ms ok 9 + int8 388 ms ok 10 + oid 196 ms ok 11 + float4 345 ms ok 12 + float8 381 ms ok 13 + bit 380 ms ok 14 + numeric 1192 ms ok 15 + txid 204 ms ok 16 + uuid 226 ms ok 17 + enum 423 ms ok 18 + money 333 ms ok 19 + rangetypes 910 ms ok 20 + pg_lsn 224 ms ok 21 + regproc 332 ms # parallel group (20 tests): md5 lseg time circle path point line numerology timetz macaddr macaddr8 polygon inet date box interval timestamp timestamptz strings multirangetypes ok 22 + strings 650 ms ok 23 + md5 65 ms ok 24 + numerology 133 ms ok 25 + point 123 ms ok 26 + lseg 67 ms ok 27 + line 128 ms ok 28 + box 441 ms ok 29 + path 122 ms ok 30 + polygon 310 ms ok 31 + circle 103 ms ok 32 + date 324 ms ok 33 + time 79 ms ok 34 + timetz 158 ms ok 35 + timestamp 527 ms ok 36 + timestamptz 595 ms ok 37 + interval 524 ms ok 38 + inet 314 ms ok 39 + macaddr 158 ms ok 40 + macaddr8 181 ms ok 41 + multirangetypes 792 ms # parallel group (12 tests): comments misc_sanity unicode mvcc xid type_sanity expressions geometry tstypes regex horology opr_sanity ok 42 + geometry 416 ms ok 43 + horology 518 ms ok 44 + tstypes 484 ms ok 45 + regex 496 ms ok 46 + type_sanity 292 ms ok 47 + opr_sanity 561 ms ok 48 + misc_sanity 59 ms ok 49 + comments 58 ms ok 50 + expressions 349 ms ok 51 + unicode 102 ms ok 52 + xid 247 ms ok 53 + mvcc 110 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 281 ms ok 55 + copyselect 101 ms ok 56 + copydml 80 ms ok 57 + insert 1394 ms ok 58 + insert_conflict 557 ms # parallel group (7 tests): create_function_c create_misc create_operator create_schema create_type create_procedure create_table ok 59 + create_function_c 31 ms ok 60 + create_misc 128 ms ok 61 + create_operator 136 ms ok 62 + create_procedure 178 ms ok 63 + create_table 1054 ms ok 64 + create_type 162 ms ok 65 + create_schema 155 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2526 ms ok 67 + create_index_spgist 1376 ms ok 68 + create_view 1604 ms ok 69 + index_including 841 ms ok 70 + index_including_gist 759 ms # parallel group (16 tests): errors create_cast create_aggregate hash_func roleattributes infinite_recurse typed_table select drop_if_exists create_function_sql create_am vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 258 ms ok 72 + create_function_sql 554 ms ok 73 + create_cast 234 ms ok 74 + constraints 1833 ms ok 75 + triggers 5303 ms ok 76 + select 465 ms ok 77 + inherit 4323 ms ok 78 + typed_table 456 ms ok 79 + vacuum 1008 ms ok 80 + drop_if_exists 512 ms ok 81 + updatable_views 3459 ms ok 82 + roleattributes 377 ms ok 83 + create_am 588 ms ok 84 + hash_func 349 ms ok 85 + errors 117 ms ok 86 + infinite_recurse 378 ms ok 87 - sanity_check 287 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit namespace case prepared_xacts select_into select_distinct union hash_index subselect transactions portals arrays update aggregates btree_index join ok 88 + select_into 538 ms ok 89 + select_distinct 542 ms ok 90 + select_distinct_on 150 ms ok 91 + select_implicit 377 ms ok 92 + select_having 258 ms ok 93 + subselect 1202 ms ok 94 + union 890 ms ok 95 + case 460 ms ok 96 + join 2735 ms ok 97 + aggregates 2411 ms ok 98 + transactions 1346 ms ok 99 + random 355 ms ok 100 + portals 1365 ms ok 101 + arrays 1521 ms ok 102 + btree_index 2519 ms ok 103 + hash_index 1015 ms ok 104 + update 1865 ms ok 105 + delete 164 ms ok 106 + namespace 448 ms ok 107 + prepared_xacts 531 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password lock object_address spgist gin collate groupingsets gist replica_identity brin identity matview generated join_hash rowsecurity privileges ok 108 + brin 1789 ms ok 109 + gin 1181 ms ok 110 + gist 1301 ms ok 111 + spgist 1147 ms ok 112 + privileges 4046 ms ok 113 + init_privs 69 ms ok 114 + security_label 310 ms ok 115 + collate 1187 ms ok 116 + matview 1996 ms ok 117 + lock 777 ms ok 118 + replica_identity 1333 ms ok 119 + rowsecurity 4000 ms ok 120 + object_address 1002 ms ok 121 + tablesample 525 ms ok 122 + groupingsets 1240 ms ok 123 + drop_operator 173 ms ok 124 + password 546 ms ok 125 + identity 1995 ms ok 126 + generated 3578 ms ok 127 + join_hash 3622 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 170 ms ok 129 + brin_multi 1049 ms # parallel group (18 tests): async collate.utf8 sysviews dbsize tid tidrangescan alter_operator tidscan tsrf misc misc_functions incremental_sort create_role alter_generic create_table_like merge collate.icu.utf8 without_overlaps ok 130 + create_table_like 1453 ms ok 131 + alter_generic 893 ms ok 132 + alter_operator 288 ms ok 133 + misc 398 ms ok 134 + async 72 ms ok 135 + dbsize 237 ms ok 136 + merge 1518 ms ok 137 + misc_functions 409 ms ok 138 + sysviews 169 ms ok 139 + tsrf 377 ms ok 140 + tid 239 ms ok 141 + tidscan 296 ms ok 142 + tidrangescan 262 ms ok 143 + collate.utf8 162 ms ok 144 + collate.icu.utf8 1578 ms ok 145 + incremental_sort 546 ms ok 146 + create_role 555 ms ok 147 + without_overlaps 2238 ms # parallel group (7 tests): collate.windows.win1252 collate.linux.utf8 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1101 ms ok 149 + psql 1100 ms ok 150 + psql_crosstab 78 ms ok 151 + amutils 69 ms ok 152 + stats_ext 2931 ms ok 153 + collate.linux.utf8 39 ms ok 154 + collate.windows.win1252 19 ms ok 155 - select_parallel 1472 ms ok 156 - write_parallel 163 ms ok 157 - vacuum_parallel 113 ms # parallel group (2 tests): subscription publication ok 158 + publication 1813 ms ok 159 + subscription 298 ms # parallel group (17 tests): portals_p2 xmlmap advisory_lock functional_deps bitmapops combocid dependency equivclass indirect_toast tsdicts guc select_views window cluster tsearch foreign_data foreign_key ok 160 + select_views 790 ms ok 161 + portals_p2 159 ms ok 162 + foreign_key 7875 ms ok 163 + cluster 1883 ms ok 164 + dependency 621 ms ok 165 + guc 773 ms ok 166 + bitmapops 579 ms ok 167 + combocid 601 ms ok 168 + tsearch 2121 ms ok 169 + tsdicts 758 ms ok 170 + foreign_data 3194 ms ok 171 + window 1355 ms ok 172 + xmlmap 285 ms ok 173 + functional_deps 476 ms ok 174 + advisory_lock 403 ms ok 175 + indirect_toast 729 ms ok 176 + equivclass 643 ms # parallel group (9 tests): jsonpath_encoding json_encoding sqljson_jsontable jsonpath sqljson json sqljson_queryfuncs jsonb_jsonpath jsonb ok 177 + json 354 ms ok 178 + jsonb 695 ms ok 179 + json_encoding 71 ms ok 180 + jsonpath 180 ms ok 181 + jsonpath_encoding 63 ms ok 182 + jsonb_jsonpath 529 ms ok 183 + sqljson 212 ms ok 184 + sqljson_queryfuncs 371 ms ok 185 + sqljson_jsontable 163 ms # parallel group (18 tests): prepare returning conversion limit plancache temp rowtypes sequence with largeobject xml copy2 truncate polymorphism rangefuncs domain plpgsql alter_table ok 186 + plancache 650 ms ok 187 + limit 375 ms ok 188 + plpgsql 2655 ms ok 189 + copy2 1179 ms ok 190 + temp 748 ms ok 191 + domain 1651 ms ok 192 + rangefuncs 1294 ms ok 193 + prepare 129 ms ok 194 + conversion 353 ms ok 195 + truncate 1186 ms ok 196 + alter_table 12100 ms ok 197 + sequence 1023 ms ok 198 + polymorphism 1189 ms ok 199 + rowtypes 850 ms ok 200 + returning 337 ms ok 201 + largeobject 1117 ms ok 202 + with 1058 ms ok 203 + xml 1152 ms # parallel group (15 tests): predicate hash_part reloptions partition_info explain memoize compression partition_aggregate stats tuplesort partition_merge partition_split partition_join partition_prune indexing ok 204 + partition_merge 2537 ms ok 205 + partition_split 3101 ms ok 206 + partition_join 4553 ms ok 207 + partition_prune 4624 ms ok 208 + reloptions 262 ms ok 209 + hash_part 96 ms ok 210 + indexing 5719 ms ok 211 + partition_aggregate 1852 ms ok 212 + partition_info 262 ms ok 213 + tuplesort 2168 ms ok 214 + explain 281 ms ok 215 + compression 1468 ms ok 216 + memoize 610 ms ok 217 + stats 2072 ms ok 218 + predicate 89 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 511 ms ok 220 + event_trigger 575 ms ok 221 - event_trigger_login 40 ms ok 222 - fast_default 501 ms ok 223 - tablespace 865 ms 1..223 # All 223 tests passed. [02:36:35.464](59.758s) ok 5 - regression tests pass # Checking port 52387 # Found port 52387 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=52387 host=/tmp/6QqOtKAEJG Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [02:36:35.519](0.055s) # 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=52386 host=/tmp/6QqOtKAEJG dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TeZm/dump1.sql [02:36:40.434](4.914s) 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/6QqOtKAEJG -p 52386 -P 52387 --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 [02:36:40.656](0.222s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [02:36:40.656](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/6QqOtKAEJG -p 52386 -P 52387 --link --check [02:36:41.448](0.792s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [02:36:41.449](0.001s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [02:36:41.449](0.001s) 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 18783 ### 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/6QqOtKAEJG -p 52386 -P 52387 --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* [02:36:43.731](2.282s) ok 12 - run of pg_upgrade --check for new instance [02:36:43.731](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/6QqOtKAEJG -p 52386 -P 52387 --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 [02:37:03.872](20.141s) ok 14 - run of pg_upgrade for new instance [02:37:03.872](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 22820 [02:37:04.005](0.133s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=52387 host=/tmp/6QqOtKAEJG dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_TeZm/dump2.sql [02:37:06.247](2.242s) ok 17 - dump after running pg_upgrade [02:37:06.327](0.081s) ok 18 - old and new dumps match after pg_upgrade # Checking port 52388 # Found port 52388 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=52388 host=/tmp/6QqOtKAEJG Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_dst_node.log [02:37:06.332](0.005s) # 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" [02:37:06.551](0.219s) Bail out! pg_ctl start failed # No postmaster PID for node "old_node" # Postmaster PID for node "new_node" is 22820 ### 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"