Thanks Magnus for the really fast response.
Your inputs have helped removed my doubts. I now went back and checked my
slave server and the WALs files are being shipped and the streaming
replication is also working. I will try a PITR test this weekend...
I have set wal_keep_segments to 3 but maybe I will bump in to 30 or some
such bigger number.
On a related note, I am see the following log entries:
2012-08-14 11:28:34 IST LOG: streaming replication successfully connected
to primary
2012-08-14 18:35:13 IST FATAL: could not receive data from WAL stream: SSL
error: sslv3 alert unexpected message
2012-08-14 18:35:18,444 8691 INFO 000000010000002D0000002E: not found
(ignored)
2012-08-14 18:35:18 IST LOG: record with zero length at 2D/2E488200
2012-08-14 18:35:18,551 8693 INFO 000000010000002D0000002E: not found
(ignored)
2012-08-14 18:35:18 IST LOG: streaming replication successfully connected
to primary
2012-08-16 12:56:07 IST FATAL: could not receive data from WAL stream: SSL
error: sslv3 alert unexpected message
2012-08-16 12:56:13,086 8753 INFO 000000010000002D000000CB: not found
(ignored)
2012-08-16 12:56:13 IST LOG: invalid magic number 0000 in log file 45,
segment 203, offset 13246464
2012-08-16 12:56:13,192 8755 INFO 000000010000002D000000CB: not found
(ignored)
2012-08-16 12:56:13 IST LOG: streaming replication successfully connected
to primary
My followup question is, do such errors affect the integrity of the slave?
Is the slave in a consistent state after such errors occur? I notice that
the corresponding WAL files are available on the slave though...
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/You-cannot-do-PITR-with-streaming-replication-true-tp5720050p5720054.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
