025_stuck_on_old_timeline_standby.log

LOG:  database system was interrupted; last known up at 2021-06-08 14:13:52 IST
LOG:  entering standby mode
LOG:  redo starts at 0/2000028
LOG:  consistent recovery state reached at 0/20000F8
LOG:  database system is ready to accept read only connections
LOG:  started streaming WAL from primary at 0/3000000 on timeline 1
LOG:  received promote request
FATAL:  terminating walreceiver process due to administrator command
LOG:  redo done at 0/20000F8
LOG:  selected new timeline ID: 2
LOG:  statement: SELECT pg_is_in_recovery() = 'f';
LOG:  archive recovery complete
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  statement: SELECT pg_is_in_recovery() = 'f';
LOG:  statement: SELECT pg_xlogfile_name(pg_current_xlog_location());
LOG:  statement: SELECT pg_switch_xlog()
LOG:  statement: SELECT '000000020000000000000003' <= last_archived_wal FROM pg_stat_archiver;
LOG:  statement: CREATE TABLE tab_int AS SELECT 1 AS a
LOG:  received immediate shutdown request
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
LOG:  archiver process (PID 66845) exited with exit code 2
LOG:  database system is shut down