public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Necessary actions after an OS upgrade
Date: Tue, 30 Sep 2025 09:16:10 -0400
Message-ID: <CANzqJaBUvJLpjXWy1Ya-CGUoO6hi+iB9cG3kx4eVmuFZ2vE=4A@mail.gmail.com> (raw)
In-Reply-To: <GV0P278MB0099C6559CE186CD3E7CF6FA8B1AA@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>
References: <GV0P278MB0099C6559CE186CD3E7CF6FA8B1AA@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>
On Tue, Sep 30, 2025 at 5:50 AM Zwettler Markus (OIZ) <
[email protected]> wrote:
> We use Crunchy Postgres for Kubernetes (CPK). With CPK 5.8, there will be
> an OS upgrade from UBI8 to UBI9 images. As described in both the Crunchy
> and Postgres documentation, conflicts due to collation version mismatches
> following an OS upgrade can lead to incorrect queries.
>
>
>
>
> https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/cluster-management/u...
>
>
> https://www.postgresql.org/docs/current/sql-altercollation.html#SQL-ALTERCOLLATION-NOTES
>
>
>
> According to the documentation, we plan to perform a “reindex database”
>
I would only rebuild text indices. Most indices are (probably) INTEGER or
BIGINT, so this would save you a lot of time
> and a “alter database refresh collation version” immediately after the
> upgrade.
>
>
>
>
>
> Is there anything else to consider? I'm wondering if this is sufficient.
>
>
>
> What about materialized views,
>
> (text) function-based indexes
>
That would be caught by REINDEX ALL, no?
> , and extensions? Couldn't problems arise here as well? None of the
> documentation addresses this. Am I thinking about this incorrectly?
>
>
>
> Ideally, I would like to have a precise list of everything that needs to
> be considered and done afterwards.
>
>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Necessary actions after an OS upgrade
In-Reply-To: <CANzqJaBUvJLpjXWy1Ya-CGUoO6hi+iB9cG3kx4eVmuFZ2vE=4A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox