2015-05-22 18:36 GMT+02:00 Piotr Gasidło qua...@barbara.eu.org:
2015-05-22 6:55 GMT+02:00 Fujii Masao masao.fu...@gmail.com:
This problem happens when WAL record is stored in separate two WAL files
and
there is no valid latter WAL file in the standby. In your case, the
former file
is
2015-05-25 11:30 GMT+02:00 Guillaume Lelarge guilla...@lelarge.info:
I currently have wal_keep_segments set to 0.
Setting this to higher value will help? As I understand: master won't
delete segment and could stream it to slave on request - so it will
help.
It definitely helps, but the
2015-05-25 15:15 GMT+02:00 Piotr Gasidło qua...@barbara.eu.org:
2015-05-25 11:30 GMT+02:00 Guillaume Lelarge guilla...@lelarge.info:
I currently have wal_keep_segments set to 0.
Setting this to higher value will help? As I understand: master won't
delete segment and could stream it to
2015-05-22 6:55 GMT+02:00 Fujii Masao masao.fu...@gmail.com:
Thanks for the report! This seems to be a bug.
This problem happens when WAL record is stored in separate two WAL files and
there is no valid latter WAL file in the standby. In your case, the former
file
is
2015-05-22 2:16 GMT+02:00 Venkata Balaji N nag1...@gmail.com:
It might be yelling about the WAL segment due to the delay in shipping it
from master to slave.
Do you have the restore_command set up in the recovery.conf file ? do you
have any automated job which is shipping WAL archives from
2015-05-22 6:55 GMT+02:00 Fujii Masao masao.fu...@gmail.com:
This problem happens when WAL record is stored in separate two WAL files and
there is no valid latter WAL file in the standby. In your case, the former
file
is 00044C4D0090 and the latter is 00044C4D0091.
Got strange problem. Unable to repeat, but got logs.
Simple master-slave using streaming replication.
Master is running. Slave is down.
Segment 00044C4D0090 was successfully archived and send
from master to slave.
Now I've started slave, and:
ay 21 21:23:37 d8 postgres[50645]: [3-1]
On Fri, May 22, 2015 at 6:52 AM, Piotr Gasidło qua...@barbara.eu.org
wrote:
Got strange problem. Unable to repeat, but got logs.
Simple master-slave using streaming replication.
Master is running. Slave is down.
Segment 00044C4D0090 was successfully archived and send
from master
On Fri, May 22, 2015 at 5:52 AM, Piotr Gasidło qua...@barbara.eu.org wrote:
Got strange problem. Unable to repeat, but got logs.
Simple master-slave using streaming replication.
Master is running. Slave is down.
Segment 00044C4D0090 was successfully archived and send
from master
