[HACKERS] in drop database, auto-vacuum and immediate shutdown concurrency scene, hot-standby server redo FATAL

hi all, I found that hot-standby server redo coredumped when the master do a concurrency test in drop database, auto-vacuum and immediate shutdown scene. Amm...the test steps as follow: 1. execute select txid_current() to force the auto vacuum launch frequenctly 2. in another session drop the dat

[HACKERS] Re: redo failed in physical streaming replication while stopping the master server

Thanks for your reply. If we only take replay for consideration, yeah, we do this header check until we've read the page first. But thanks to the master xlog generator, we know that: when we try advance XLOG insert buffer (page), we treate the new page header as short header at first. then we use

[HACKERS] redo failed in physical streaming replication while stopping the master server

Hi all, Issue: I use hot standby stream replication in PostgreSQL 9.2.X. And after i shut down the master server in fast stop mode, i compared the xlog dump files between the master and slave and found that the shutdown checkpoint was not replicated to the slave。 Then i check the pg_log in slave a