David Steele

I think this is fixed by PR #1960. Thoughts, @woblerr?

Closing this issue since there is not enough information to resolve. It is likely environmental, but hard to say.

This definitely seems like a good idea. There are two thing that will make it a bit tricky: 1) Sometimes the option is not new but just one of the...

> for criteria met you don't have such a message. Not very convenient for grepping logs. I hoped for will be expired message Hmm, but I think that's what we...

This is basically what the start/stop command do. When a stanza is stopped it is not possible to write to the repo. That's probably not too clear from the docs,...

> Is this something which can be implemented? In theory, yes, but only at a major cost to feature work. As implemented, the remotes are very "smart" which means that...

> all 2.x versions are api-compatible with each other, and api-breaking changes would only happen between 2.x and 3.y Again, this can only happen with a lot more development resources...

Looks like the terminal session that was running pgbackrest got terminated. If it is not running under cron you might try using `screen`.

> So it that possible add a custom parameter for the SSH timeout on pgbackrest conf file No, but you should be able to set whatever client settings you need...

> But I don't want to connect to physical servers, because I've configured backup standby, and so after switchover or failovers, I must to change pgbackrest.conf file each time. No,...