David Steele

@cbrianpace I would like to get #85 committed. Would you mind doing a quick review?

We have considered this feature but it is not currently on the roadmap.

I agree that this is a bug an we are aware of it but most users run expire with backup so it doesn't come up. In order for use to...

This is on my radar and I think it is a good change but it will be a few weeks or more before I can get to it. You hit...

I have had a quick look through. There are certainly more changes than I was expecting (e.g. using a KeyValue instead of just outputting using JsonWrite). That's probably OK since...

I've looked at this a number of times but each time I hold off on comment because I don't think this is what we want -- but I'm not exactly...

Also, tests are definitely not happy: https://github.com/pgbackrest/pgbackrest/actions/runs/14105373523

This appears the be some sort of permissions issue on `/data/backups/archive/staging/13-1/0000000100000503` while trying to check the archive. The backup succeeds so it does not look like a more general error....

I looked up the error and it says LIBSSH2_ERROR_SOCKET_SEND, so looks like a network error.

> /data/backups/archive/staging/13-1/0000000100000503 Yes, pgBackRest is trying to list the files in this directory to be sure the WAL files required to make the backup consistent have been pushed.