David Steele

> is it likely that your fix would resolve this as well? I can compile your branch and test of course :) I believe the fix will work for this...

> No chance of getting this fix out a little sooner than the next regular release I suppose? Probably not, but we'll discuss it. We decided not to delay the...

We are not planning to support an "official" Docker image. There are already several Dockerized pgBackRest solutions. In addition to the link @woblerr posted, there is also Crunchy Containers (https://github.com/CrunchyData/crunchy-containers).

It looks like we are sending a DELETE request and the reply indicates that there is response content to be read `Content-Type: text/html; charset=UTF-8`/`Transfer-Encoding: chunked` but the server sends nothing...

> I think the "several times" refers to pgBackRest retrying the request because of the invalid server response Yes, exactly. The first delete fails and then we retry for `io-timeout`...

OK, good to know! Hopefully people with the same issue will be able to find this.

> there is a built-in --filter option, but i had bad luck using it @kolbasky Have you tried this recently? I believe we fixed a bug in this area a...

> Any command/way for getting the archived WAL file path in repo (i.e when archive command is executed by postgres) Not specifically, you can do what @kolbasky suggested but it...

@kolbasky I was able to reproduce it. I created PR #1871 with a fix.

Looks like a bug to me as well, but not sure how to go about fixing it yet. It could be that we would ignore the history in this case...