Complete WAL-E support

[zalando]

Complete WAL-E support

[CyberDem0n]

postgres.yaml:

postgresql:
  parameters:
    archive_mode: "on"
    archive_command: envdir "/path/to/env-dir" wal-e wal-push "%p"
  recovery_conf:
    restore_command: envdir "/path/to/env-dir" wal-e wal-fetch "%f" "%p"

Although don't forget to create a cronjob, which will do envdir "/path/to/env-dir" wal-e backup-push "/path/to/postgres/data/directory"

Please read about envdir in wal-e documentation: https://github.com/wal-e/wal-e/

[CyberDem0n]

Replicas are executing not archive_command but restore_command

[alexeyklyukin]

Hi Josh,

Take a look at scrips/restore.py. The code there deals with initialization of new replicas. It was intentionally moved out of the core Patroni to avoid requiring unnecessary dependencies for non-AWS use-cases. The WAL-E support relies on the archive/restore command being properly configured in Patroni, as well as regular base backups (part of the Docker container in the Spilo project).

[jberkus]

Oh, I see!

How does restore integrate with the rest of patroni?

[LappleApple]

@jberkus @alexeyklyukin This issue's almost a year old -- can we resolve or close?

[alexeyklyukin]

From my POV it's not an issue anymore.

[LappleApple]

OK, I'll close and you guys can reopen if necessary.

[Firefishy]

Is there any public documentation on how to use patroni + wal-e? I am failing to get it configured.

[Firefishy]

@CyberDem0n Thank you. Would that not also result in slaves pushing archives via wal-e? (Or is that not a concern because the WAL files are identical?)