postgresql_Thu_Patch.log

application/octet-stream

Filename: postgresql_Thu_Patch.log
Type: application/octet-stream
Part: 0
Message: Re: Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly
LOG:  database system was shut down at 2016-11-24 03:02:16 UTC
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
LOG:  database system was interrupted; last known up at 2016-11-24 03:02:17 UTC
FATAL:  the database system is starting up
FATAL:  the database system is starting up
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000002.history': No such file or directory
LOG:  entering standby mode
FATAL:  the database system is starting up
FATAL:  the database system is starting up
LOG:  restored log file "000000010000000000000002" from archive
LOG:  redo starts at 0/2000020
FATAL:  the database system is starting up
LOG:  consistent recovery state reached at 0/20000E0
LOG:  database system is ready to accept read only connections
LOG:  database system was interrupted while in recovery at log time 2016-11-24 03:02:17 UTC
HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
FATAL:  the database system is starting up
FATAL:  the database system is starting up
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000002.history': No such file or directory
LOG:  entering standby mode
FATAL:  the database system is starting up
FATAL:  the database system is starting up
LOG:  restored log file "000000010000000000000002" from archive
LOG:  redo starts at 0/2000020
LOG:  consistent recovery state reached at 0/3000000
LOG:  database system is ready to accept read only connections
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000010000000000000003': No such file or directory
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000002.history': No such file or directory
LOG:  streaming replication successfully connected to primary
FATAL:  replication terminated by primary server
LOG:  restored log file "000000010000000000000003" from archive
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000010000000000000004': No such file or directory
LOG:  restored log file "00000002.history" from archive
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000003.history': No such file or directory
LOG:  restored log file "00000002.history" from archive
LOG:  new target timeline is 2
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000020000000000000004': No such file or directory
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000010000000000000004': No such file or directory
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000003.history': No such file or directory
LOG:  streaming replication successfully connected to primary
LOG:  invalid contrecord length 56 in log file 0, segment 4, offset 0
FATAL:  terminating walreceiver process due to administrator command
LOG:  restored log file "000000020000000000000003" from archive
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000020000000000000004': No such file or directory
LOG:  record with zero length at 0/4000060
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/000000020000000000000004': No such file or directory
cp: cannot stat `/data/akapila/workspace/as92/installation/bin/data/archive/00000003.history': No such file or directory
LOG:  streaming replication successfully connected to primary