Re: Fwd: Adding more detail to pg_upgrade documentation

From: Jack DeVries <jdevries3133(at)gmail(dot)com>
To: Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
Date: 2022-06-03 20:18:10
Message-ID: Yppsghp3z8pMsrDH@Jacks-MacBook-Pro.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-docs

Hi Nikhil,

From the pgupgrade docs:

> 9. Prepare for standby server upgrades
>
> If you are upgrading standby servers using methods outlined in section
> Step 11, verify that the old standby servers are caught up by running
> pg_controldata against the old primary and standby clusters. Verify
> that the “Latest checkpoint location” values match in all clusters.
> (There will be a mismatch if old standby servers were shut down before
> the old primary or if the old standby servers are still running.)
> Also, make sure wal_level is not set to minimal in the postgresql.conf
> file on the new primary cluster.

(source: https://www.postgresql.org/docs/devel/pgupgrade.html)

I'm a new contributor so please forgive me if I'm on the wrong track,
but if you follow this step, won't you also be ensuring that replication
slots do not need to be migrated, since you've just ensured that standby
clusters are in sync with the primary cluster? Please let me know if I'm
missing anything!

Thank You,
Jack DeVries

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Raj kumar 2022-06-03 21:49:02 Changing Data Type on Production Database - Impact
Previous Message Raj kumar 2022-06-03 06:49:42 Logical Replication - Initial Snapshot Only mode

Browse pgsql-docs by date

  From Date Subject
Next Message Nikhil Shetty 2022-06-04 09:38:58 Re: Fwd: Adding more detail to pg_upgrade documentation
Previous Message Tom Lane 2022-06-03 17:55:52 Re: Proposal to improve uniq function documentation in intarray extension