David Steele

> ERROR: [052]: unable to sync file 'pgbackup/instance1/archive/pginstance1/archive.info.pgbackrest.tmp' after write: [28] No space left on device This error is coming from your storage. You'll need to figure out why it...

Yeah, I was about to suggest that it was a disk space issue. This is an area we are working on -- basically if a file transfer fails in the...

What was the error in the `archive-push-async` log?

It is on the pg host. The attached file is from the repo host. This is async archiving, right?

So I've been trying for a while to reproduce this with no luck. When out of space I just get a regular error. One thing that occurs to me. We...

Yes, the SSH connections should be setup before running pgBackRest, as shown here: https://pgbackrest.org/user-guide.html#repo-host/setup-ssh.

The only idea we have at this point is to use TLS instead of SSH. The SSH connection can be noisy because the system can write random message into it,...

We believe that the errors being presented here are not the original error, but are generate during cleanup after the original error. 0f7b6a3344b6 should help with this by avoiding cleanup...

This seems like a good idea but I'm not sure auto-transforming options into commands is a good idea. It leads to some surprising behaviors, e.g.: ``` $ test/bin/none/pgbackrest --version --help...

No, there's nothing like this in the backlog right now. I think configuration could be a bit tricky unless we just used the `repo-*` options somehow -- and I don't...