Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
| От | David Rowley |
|---|---|
| Тема | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Дата | |
| Msg-id | CAApHDvozYU11A7T5XxrzajA6-rqrzRZXfbtToAOu+U_S-Btj=g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) (Adrian Klaver <adrian.klaver@aklaver.com>) |
| Ответы |
Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Список | pgsql-general |
On Sat, 25 Oct 2025 at 17:36, Adrian Klaver <adrian.klaver@aklaver.com> wrote: > I am not following, from your previous post: > > "Beta versions are meant for test instances. It'd be > good if people encouraged their use more often rather than pushing > people to defer til GA" > > That seems to be the opposite of what you say above. I think you think that because you misunderstood what I said in [1]. I'll rephrase it for you: Because people promote the .0 as not yet production-ready, it means that fewer people bother testing with beta and RC versions. Lack of beta testing is what causes .0 to contain more bugs than it otherwise might, so my suggestion is that we should be encouraging people to run beta and RC in their test environments to try to increase the stability of .0 versions. I struggle to imagine anyone with any respect for the PostgreSQL project disagreeing with that, so I suspect you and Johnson must have misunderstood. Also, I was highlighting that I agreed with the paradox pointed out by Ron. Clear? > >> 3) Progress happens and you need to keep up. A little caution is good > >> thing though, especially if you are the one who is being held > >> responsible for any adverse outcomes. > > > > We're talking test servers here. I assume they can be recreated > > without too much trouble. > > Yes, but the OP was talking about upgrading a production database > directly to 18. That was what my reply was referring to and what I was > counseling against. You should pay more attention to the quotes above my reply. I don't see any of my replies quoting anything about upgrading a production database to 18.0. David [1] https://postgr.es/m/CAApHDvo5pLSwD4JVxW8t94Vc88djKrrSyrL-GbQJ=hb2NVT5zg@mail.gmail.com
В списке pgsql-general по дате отправления: