[03:26:57.771](0.021s) # testing using transfer mode --link # Checking port 64644 # Found port 64644 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=64644 host=/tmp/dPt7NCBLJT Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_old_node.log [03:26:57.777](0.006s) # 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 6560 [03:26:59.488](1.711s) ok 1 - check locales in original cluster # Running: createdb regression\"\  !"#$%&'()*+,-\\"\\\ [03:26:59.567](0.078s) ok 2 - created database with ASCII characters from 1 to 45 # Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [03:26:59.651](0.084s) ok 3 - created database with ASCII characters from 46 to 90 # Running: createdb regression[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ [03:26:59.709](0.058s) ok 4 - created database with ASCII characters from 91 to 127 [03:26:59.717](0.008s) # running regression tests in old instance # using postmaster on /tmp/dPt7NCBLJT, port 64644 ok 1 - test_setup 478 ms # parallel group (20 tests): char txid oid varchar pg_lsn name uuid text int2 boolean int4 money regproc float4 int8 float8 enum bit rangetypes numeric ok 2 + boolean 276 ms ok 3 + char 153 ms ok 4 + name 193 ms ok 5 + varchar 171 ms ok 6 + text 225 ms ok 7 + int2 251 ms ok 8 + int4 277 ms ok 9 + int8 337 ms ok 10 + oid 163 ms ok 11 + float4 308 ms ok 12 + float8 371 ms ok 13 + bit 393 ms ok 14 + numeric 1304 ms ok 15 + txid 161 ms ok 16 + uuid 206 ms ok 17 + enum 387 ms ok 18 + money 286 ms ok 19 + rangetypes 1045 ms ok 20 + pg_lsn 176 ms ok 21 + regproc 288 ms # parallel group (20 tests): md5 lseg circle line macaddr path time macaddr8 point timetz numerology polygon inet date box interval timestamp timestamptz strings multirangetypes ok 22 + strings 668 ms ok 23 + md5 59 ms ok 24 + numerology 228 ms ok 25 + point 157 ms ok 26 + lseg 86 ms ok 27 + line 98 ms ok 28 + box 353 ms ok 29 + path 113 ms ok 30 + polygon 255 ms ok 31 + circle 92 ms ok 32 + date 278 ms ok 33 + time 114 ms ok 34 + timetz 167 ms ok 35 + timestamp 513 ms ok 36 + timestamptz 615 ms ok 37 + interval 373 ms ok 38 + inet 269 ms ok 39 + macaddr 109 ms ok 40 + macaddr8 155 ms ok 41 + multirangetypes 936 ms # parallel group (12 tests): misc_sanity unicode comments mvcc tstypes type_sanity expressions xid geometry horology regex opr_sanity ok 42 + geometry 370 ms ok 43 + horology 400 ms ok 44 + tstypes 162 ms ok 45 + regex 405 ms ok 46 + type_sanity 188 ms ok 47 + opr_sanity 538 ms ok 48 + misc_sanity 58 ms ok 49 + comments 81 ms ok 50 + expressions 256 ms ok 51 + unicode 77 ms ok 52 + xid 262 ms ok 53 + mvcc 98 ms # parallel group (5 tests): copydml copyselect copy insert_conflict insert ok 54 + copy 223 ms ok 55 + copyselect 142 ms ok 56 + copydml 105 ms ok 57 + insert 1492 ms ok 58 + insert_conflict 557 ms # parallel group (7 tests): create_function_c create_schema create_operator create_misc create_type create_procedure create_table ok 59 + create_function_c 48 ms ok 60 + create_misc 211 ms ok 61 + create_operator 202 ms ok 62 + create_procedure 234 ms ok 63 + create_table 1563 ms ok 64 + create_type 221 ms ok 65 + create_schema 186 ms # parallel group (5 tests): index_including_gist index_including create_index_spgist create_view create_index ok 66 + create_index 2467 ms ok 67 + create_index_spgist 1041 ms ok 68 + create_view 1541 ms ok 69 + index_including 815 ms ok 70 + index_including_gist 698 ms # parallel group (16 tests): create_cast errors hash_func select roleattributes typed_table create_aggregate infinite_recurse create_am create_function_sql drop_if_exists vacuum constraints updatable_views inherit triggers ok 71 + create_aggregate 404 ms ok 72 + create_function_sql 567 ms ok 73 + create_cast 108 ms ok 74 + constraints 2136 ms ok 75 + triggers 5442 ms ok 76 + select 332 ms ok 77 + inherit 4819 ms ok 78 + typed_table 400 ms ok 79 + vacuum 1087 ms ok 80 + drop_if_exists 578 ms ok 81 + updatable_views 3569 ms ok 82 + roleattributes 354 ms ok 83 + create_am 472 ms ok 84 + hash_func 257 ms ok 85 + errors 153 ms ok 86 + infinite_recurse 464 ms ok 87 - sanity_check 127 ms # parallel group (20 tests): select_distinct_on delete select_having random select_implicit namespace select_distinct select_into case prepared_xacts union subselect hash_index portals arrays transactions update btree_index aggregates join ok 88 + select_into 826 ms ok 89 + select_distinct 818 ms ok 90 + select_distinct_on 173 ms ok 91 + select_implicit 483 ms ok 92 + select_having 313 ms ok 93 + subselect 1757 ms ok 94 + union 1693 ms ok 95 + case 875 ms ok 96 + join 4122 ms ok 97 + aggregates 3583 ms ok 98 + transactions 2404 ms ok 99 + random 421 ms ok 100 + portals 1821 ms ok 101 + arrays 2086 ms ok 102 + btree_index 3315 ms ok 103 + hash_index 1788 ms ok 104 + update 2871 ms ok 105 + delete 242 ms ok 106 + namespace 584 ms ok 107 + prepared_xacts 1022 ms # parallel group (20 tests): init_privs drop_operator security_label tablesample password object_address lock replica_identity collate groupingsets gist spgist gin matview identity generated brin join_hash privileges rowsecurity ok 108 + brin 4125 ms ok 109 + gin 1557 ms ok 110 + gist 1535 ms ok 111 + spgist 1551 ms ok 112 + privileges 4744 ms ok 113 + init_privs 94 ms ok 114 + security_label 320 ms ok 115 + collate 1380 ms ok 116 + matview 2257 ms ok 117 + lock 914 ms ok 118 + replica_identity 1252 ms ok 119 + rowsecurity 4750 ms ok 120 + object_address 739 ms ok 121 + tablesample 482 ms ok 122 + groupingsets 1400 ms ok 123 + drop_operator 249 ms ok 124 + password 716 ms ok 125 + identity 2363 ms ok 126 + generated 3816 ms ok 127 + join_hash 4140 ms # parallel group (2 tests): brin_bloom brin_multi ok 128 + brin_bloom 196 ms ok 129 + brin_multi 1554 ms # parallel group (18 tests): async dbsize collate.utf8 sysviews tsrf tidrangescan tid tidscan alter_operator misc_functions create_role misc incremental_sort alter_generic collate.icu.utf8 create_table_like merge without_overlaps ok 130 + create_table_like 1423 ms ok 131 + alter_generic 762 ms ok 132 + alter_operator 413 ms ok 133 + misc 463 ms ok 134 + async 70 ms ok 135 + dbsize 91 ms ok 136 + merge 1799 ms ok 137 + misc_functions 432 ms ok 138 + sysviews 233 ms ok 139 + tsrf 240 ms ok 140 + tid 293 ms ok 141 + tidscan 320 ms ok 142 + tidrangescan 250 ms ok 143 + collate.utf8 195 ms ok 144 + collate.icu.utf8 1407 ms ok 145 + incremental_sort 623 ms ok 146 + create_role 448 ms ok 147 + without_overlaps 2278 ms # parallel group (7 tests): collate.linux.utf8 collate.windows.win1252 amutils psql_crosstab psql rules stats_ext ok 148 + rules 1808 ms ok 149 + psql 1779 ms ok 150 + psql_crosstab 53 ms ok 151 + amutils 47 ms ok 152 + stats_ext 3558 ms ok 153 + collate.linux.utf8 26 ms ok 154 + collate.windows.win1252 29 ms ok 155 - select_parallel 1220 ms ok 156 - write_parallel 115 ms ok 157 - vacuum_parallel 107 ms # parallel group (2 tests): subscription publication ok 158 + publication 2481 ms ok 159 + subscription 247 ms # parallel group (17 tests): portals_p2 xmlmap advisory_lock combocid functional_deps bitmapops tsdicts select_views indirect_toast equivclass dependency guc window tsearch cluster foreign_data foreign_key ok 160 + select_views 539 ms ok 161 + portals_p2 134 ms ok 162 + foreign_key 8187 ms ok 163 + cluster 1525 ms ok 164 + dependency 628 ms ok 165 + guc 703 ms ok 166 + bitmapops 427 ms ok 167 + combocid 402 ms ok 168 + tsearch 1493 ms ok 169 + tsdicts 521 ms ok 170 + foreign_data 3132 ms ok 171 + window 1456 ms ok 172 + xmlmap 187 ms ok 173 + functional_deps 402 ms ok 174 + advisory_lock 297 ms ok 175 + indirect_toast 577 ms ok 176 + equivclass 606 ms # parallel group (9 tests): jsonpath_encoding json_encoding jsonpath sqljson sqljson_jsontable sqljson_queryfuncs json jsonb_jsonpath jsonb ok 177 + json 331 ms ok 178 + jsonb 644 ms ok 179 + json_encoding 59 ms ok 180 + jsonpath 105 ms ok 181 + jsonpath_encoding 45 ms ok 182 + jsonb_jsonpath 409 ms ok 183 + sqljson 211 ms ok 184 + sqljson_queryfuncs 281 ms ok 185 + sqljson_jsontable 231 ms # parallel group (18 tests): prepare limit conversion returning plancache temp sequence with truncate rowtypes copy2 polymorphism largeobject rangefuncs xml domain plpgsql alter_table ok 186 + plancache 446 ms ok 187 + limit 333 ms ok 188 + plpgsql 3198 ms ok 189 + copy2 1131 ms ok 190 + temp 714 ms ok 191 + domain 1683 ms ok 192 + rangefuncs 1399 ms ok 193 + prepare 220 ms ok 194 + conversion 339 ms ok 195 + truncate 1059 ms ok 196 + alter_table 9870 ms ok 197 + sequence 858 ms ok 198 + polymorphism 1278 ms ok 199 + rowtypes 1110 ms ok 200 + returning 403 ms ok 201 + largeobject 1312 ms ok 202 + with 1017 ms ok 203 + xml 1411 ms # parallel group (15 tests): predicate explain hash_part reloptions memoize partition_info compression partition_merge partition_aggregate partition_split stats tuplesort partition_join indexing partition_prune ok 204 + partition_merge 1033 ms ok 205 + partition_split 2413 ms ok 206 + partition_join 4736 ms ok 207 + partition_prune 5200 ms ok 208 + reloptions 302 ms ok 209 + hash_part 302 ms ok 210 + indexing 4903 ms ok 211 + partition_aggregate 1849 ms ok 212 + partition_info 480 ms ok 213 + tuplesort 3474 ms ok 214 + explain 301 ms ok 215 + compression 777 ms ok 216 + memoize 479 ms ok 217 + stats 2703 ms ok 218 + predicate 299 ms # parallel group (2 tests): oidjoins event_trigger ok 219 + oidjoins 523 ms ok 220 + event_trigger 573 ms ok 221 - event_trigger_login 140 ms ok 222 - fast_default 407 ms ok 223 - tablespace 2165 ms 1..223 # All 223 tests passed. [03:28:02.283](62.566s) ok 5 - regression tests pass # Checking port 64645 # Found port 64645 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=64645 host=/tmp/dPt7NCBLJT Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_new_node.log [03:28:02.286](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=64644 host=/tmp/dPt7NCBLJT dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_eZ7A/dump1.sql [03:28:06.806](4.520s) 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/dPt7NCBLJT -p 64644 -P 64645 --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 [03:28:06.957](0.151s) ok 7 - run of pg_upgrade --check for new instance with incorrect binary path [03:28:06.957](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/dPt7NCBLJT -p 64644 -P 64645 --link --check [03:28:07.672](0.715s) ok 9 - invalid database causes failure status (got 1 vs expected 1) [03:28:07.672](0.000s) ok 10 - invalid database causes failure stdout /(?^:invalid)/ [03:28:07.673](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 19088 ### 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/dPt7NCBLJT -p 64644 -P 64645 --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* [03:28:09.542](1.870s) ok 12 - run of pg_upgrade --check for new instance [03:28:09.543](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/dPt7NCBLJT -p 64644 -P 64645 --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 [03:28:31.849](22.306s) ok 14 - run of pg_upgrade for new instance [03:28:31.849](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 23339 [03:28:31.976](0.127s) ok 16 - check that locales in new cluster match original cluster # Running: pg_dumpall --no-sync -d port=64645 host=/tmp/dPt7NCBLJT dbname='postgres' -f /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_eZ7A/dump2.sql [03:28:34.032](2.055s) ok 17 - dump after running pg_upgrade [03:28:34.116](0.084s) ok 18 - old and new dumps match after pg_upgrade # Checking port 64646 # Found port 64646 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=64646 host=/tmp/dPt7NCBLJT Log file: /tmp/cirrus-ci-build/build/testrun/pg_upgrade/002_pg_upgrade/log/002_pg_upgrade_dst_node.log [03:28:34.120](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" [03:28:34.282](0.161s) Bail out! pg_ctl start failed # No postmaster PID for node "old_node" # Postmaster PID for node "new_node" is 23339 ### 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"