| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Ebin Jozer <ebinjozer(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgresql community edition upgrade |
| Date: | 2022-10-13 12:51:53 |
| Message-ID: | 3DEF677C-D70F-43F5-A912-4DA0C8C949D3@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Oct 13, 2022, at 3:42 AM, Ebin Jozer <ebinjozer(at)gmail(dot)com> wrote:
>
> We have master and slave environment. So for upgrade we have upgrade first in slave and then in master environment. Please confirm
Depends on your HA requirements.
Easiest: shut down primary and all db access, upgrade one, bring it back up as primary, upgrade other and bring it back online as replica.
Harder: use a replication scheme that works across versions (publish/subscribe, pglogical, londiste, bucardo) so that you can bring up a new replica on the new version, switch over to it with minimal downtime (just enough to make sure changes from master have been replicated), then turn the former primary into a new replica.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albin Ary | 2022-10-13 13:10:34 | Gui strange behaviour - trying to bring all rows |
| Previous Message | Matheus Alcantara | 2022-10-13 11:17:30 | Re: pgAdmin hangs while there is a long running process marked red |