| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Bala M <krishna(dot)pgdba(at)gmail(dot)com> |
| Cc: | "adrian(dot)klaver(at)aklaver(dot)com" <adrian(dot)klaver(at)aklaver(dot)com>, chris+google(at)qwirx(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Date: | 2025-10-24 12:58:57 |
| Message-ID: | CAKAnmm+DcNS_FTGOG9Q3WUQGxxukhqf1rz5jrqzAk0z9W5d59A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 23, 2025 at 10:51 AM Bala M <krishna(dot)pgdba(at)gmail(dot)com> wrote:
> Any advice, recommendations, or shared experiences from others who have
> performed similar migrations would be greatly appreciated.
Some related advice: put some system in place to make sure you are always
running the latest revision in whatever major version you end up. See:
https://www.postgresql.org/support/versioning/
In particular, note this part:
*The community considers performing minor upgrades to be less risky than
continuing to run an old minor version.*
You also want to put something in place to make sure your major version
does not fall so far behind again. You don't need to upgrade every year,
but certainly target a major upgrade every 2-3 years. As you will discover,
the major upgrade process is going to be much easier than this current
upgrade we are talking about in this thread.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-10-24 13:01:11 | Re: Why is this query touching 4gb of buffers? |
| Previous Message | hubert depesz lubaczewski | 2025-10-24 12:56:12 | Re: Why is this query touching 4gb of buffers? |