Lardière Sébastien

While trying to understand the problem, I setted up the log level to DEBUG then TRACE to get the detailed error message from the S3 provider (which is not logged...

So, another problem is that the detailed error message provided by the S3 provider (scaleway here) isn't traced by pgbackrest. While trying to understand the problem with s3cmd: ~~~ s3cmd...

Here's the full log, without TRACE : [lsi-archive-push-async.log.gz](https://github.com/pgbackrest/pgbackrest/files/9467634/lsi-archive-push-async.log.gz) The queue size is lower than the free space, about a half only. But one of the problem is the large number...

Actually, the volume was filled up the 2022-08-23 at 08:27 (PG was stopped) ; Then I had to drop some « old WAL » to restart, and remove archiving setup...

I don't think so, no ; actually, I don't need it, because trigger was not the solution, but it's still a bug, afaik.