Questions about 3.0 release

[OrangeDog]

I tried asking on Slack, but the channel is dead, and I don't have Telegram.

How exactly does the new failover storage work?
Does it automatically sync the failover back to the primary storage once it comes back, or does that need to be set up externally?
Do you get warnings (or higher) logged when it's failing-over, or is it silent?
Can you set a limit for the amount of failover to use before it returns to the previous behaviour, making the DB retry until it's working again?

Also, I assume due to no mention in the release notes, that there's no breaking changes and you can just upgrade without changing anything?

[x4m]

@rdjjke can you please answer some questions about the feature that you implemented?
And maybe let's consider adding these answers to documentation.

[OrangeDog]

Can someone at least confirm that the upgrade path is just "install the new version"?

[x4m]

wal-push and wal-fetch are forward and backward compatible across all 0.1.4+ versions.
Backups are backward-compatible: wal-g 3.0.0 can restore any backup made by any release of wal-g since 0.1.4 and some releases of pgbackrest.
Sorry for our docs, I hope we will improve it.

[x4m]

There are some issues with backup-list --json --details when reading backup metadata of older versions.

[jorsol]

Hi @x4m, what kind of issues with backup-list --json --details?