-
Notifications
You must be signed in to change notification settings - Fork 76
Closed
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerspg:resiliencyHelps to strengthen Fly PostgresHelps to strengthen Fly Postgres
Description
Add support for PG Barman
This should be fairly straight forward to support.
- PG Barman will need to run in its own Machine.
- It will need to be fronted with haproxy just like a normal member so connections that hit this Machine will still be routed correctly.
- The Init/Post Init process will need to be adjusted such that only haproxy and Barman are initialized.
Why Barman over something like Wal-G
- Repmgr works with Barman out of the box.
- Wal-G is expected to run next to the main database which can lead to resource contention.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerspg:resiliencyHelps to strengthen Fly PostgresHelps to strengthen Fly Postgres