Re: Support for N synchronous standby servers - take 2

Hello,
I did apply the patch to HEAD and tried to setup basic async replication.But
i got an error. Turned on logging for details below.

Unpatched Primary Log
LOG: database system was shut down at 2015-09-12 13:41:40 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started

Unpatched Standby log
LOG: entering standby mode
LOG: redo starts at 0/2000028
LOG: invalid record length at 0/20000D0
LOG: started streaming WAL from primary at 0/2000000 on timeline 1
LOG: consistent recovery state reached at 0/20000F8
LOG: database system is ready to accept read only connections

Patched Primary log
LOG: database system was shut down at 2015-09-12 13:50:17 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: server process (PID 17317) was terminated by signal 11: Segmentation
fault
LOG: terminating any other active server processes
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: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2015-09-12 13:50:18
IST
FATAL: the database system is in recovery mode
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: invalid record length at 0/3000098
LOG: redo is not required
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: server process (PID 17343) was terminated by signal 11: Segmentation
fault
LOG: terminating any other active server processes

Patched Standby log
LOG: database system was interrupted; last known up at 2015-09-12 13:50:16
IST
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: entering standby mode
LOG: redo starts at 0/2000028
LOG: invalid record length at 0/20000D0
LOG: started streaming WAL from primary at 0/2000000 on timeline 1
FATAL: could not receive data from WAL stream: server closed the connection
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

FATAL: could not connect to the primary server: FATAL: the database system
is in recovery mode

Not sure if there is something i am missing which causes this.
regards
Sameer

--
View this message in context: http://postgresql.nabble.com/Support-for-N-synchronous-standby-servers-take-2-tp5849384p5865685.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.