> On 02/18/2017 02:06, Tomas Vondra wrote:
>
> What do you mean by "became unavailable"? The restore_command may be called
> for segments that do not exist - that's expected, and I suspect the "gzip:
> stdin: unexpected end of file" error messages are caused by that.
>
Sorry for my unclear de
On 02/18/2017 10:01 PM, Nikolay Petrov wrote:
Hot standby server was started with new recovery.conf, reached
consistent recovery state and resumed to restore WAL segments from
archive. When couple of next wal segments became unavailable slave
server just "skipped" them, instead to start streaming
Hello everyone.
I use postgresql 9.6.1 running under a debian 8 (master - slave hot standby
streaming replication).
I found out unexpected WAL-archive restore behaviour.
master:
wal_level = replica
archive_mode = on
archive_command = 'gzip < %p > /var/lib/postgres/archives/%f'
slave
