Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Ron Johnson <ronljohnsonjr@gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-10-24T15:00:35Z
Lists: pgsql-general
On Fri, Oct 24, 2025 at 10:54 AM Adrian Klaver <adrian.klaver@aklaver.com> wrote: > On 10/24/25 05:53, Greg Sabino Mullane wrote: > > On Thu, Oct 23, 2025 at 11:49 AM Adrian Klaver > > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote: > > > > I am not sure version 18 would a good choice at this time, it has > > just been released and has no bug fix releases against it yet. Given > > the > > other complications in your upgrade, OS upgrade and multi-version > > jump, I don't think you want to add a brand new version to the mix. > > Postgres > > 17 on the other hand has been out a year and has had 6 bug/security > > fixes. It is probably a more stable target version. > > > > > > I hear your concern, but I'm pretty confident in v18. Additionally, they > > Which is pretty much the criteria for a GA release, confidence that it > is ready to face the general public. That is not the same thing as it > being guaranteed bug free. Only time facing the manipulations of said > public proves how many bugs there are and how bad they are. > "Never trust a .0 release with important data" is just as true in 2025 as it was in 1985. That's a chicken and egg problem, though, isn't it? -- Death to <Redacted>, and butter sauce. Don't boil me, I'm still alive. <Redacted> lobster!