3 ms·
When reading this I wonder how to do this: OS or Postgres updates with one normal Postgres (or a typical master+slave setup) without downtime and without using
by therealmarv 10y ago
When reading this I wonder how to do this: OS or Postgres updates with one normal Postgres (or a typical master+slave setup) without downtime and without using Postgres BDR. Does somebody now?
- andruby 10y agoWe have one master PG database and handle upgrades during "planned downtime" during off-peak hours (during weekend nights our B2B app is relatively empty). We prep a new instance with the upgrades in place, and then load over the production data during downtime.
- colanderman 10y agoOS upgrades, sure, just use two systems with one of the existing async rep solutions between them. You'll need to make the master read-only for a brief period before failover as the slave "catches up" with the master. Online PG upgrades aren't (until now) possible because the binary log format changes. But pglogical (which underpins BDR) solves this issue: https://2ndquadrant.com/en/resources/pglogical/ https://2ndquadrant.com/en/resources/pglogical/ Process would be the same as an OS upgrade (brief period of read-only availability required), but you can do it on one machine.
- pgaddict 10y agoSomething like that is possible by using UDR (think BDR but only in one direction): https://wiki.postgresql.org/images/a/a8/Udr-pgconf.pdf https://wiki.postgresql.org/images/a/a8/Udr-pgconf.pdf