David Steele

> If the changes you made to the configuration are working then it was reloaded. To be a little clearer, the only options valid for the server are TLS setttings,...

I just played with this and you should see a rather obvious restart message when the config is reloaded, e.g.: ``` -------------------PROCESS START------------------- P00 INFO: server command begin 2.49dev: --exec-id=744-242f7aed...

You can also see an explicit reload message at detail log level.

The most impactful thing you can do here is use a faster compression algorithm, e.g. `zst` (generally about five times faster than gz for the same compression ratio). `lz4` is...

> a backup with 2 CPUs was faster than with more or fewer CPUs, and a backup with 2 CPUs with max 2 processes was faster than with 6 CPUs...

Right now the only practical way to throttle is by setting `process-max` appropriately. Compression is expensive and it limits IO pretty effectively. If IO is maxed when `process-max=1` you may...

The client and server certs for each pair must be generated with the same CA. Other than that, you can use different CAs if you prefer and like making things...

> Maybe we could adjust the expire command message to tell the users that this was an un-resumable backup to remove? This would be more complicated that it is worth,...

OK, I've added a card for the wording change: https://github.com/pgbackrest/pgbackrest/projects/2#card-92022329. Still not very happy with anything I've though of.

What version are you running? This should have been addressed in 2.48 by 9d3a6059.