public inbox for [email protected]
help / color / mirror / Atom feedNecessary actions after an OS upgrade
2+ messages / 2 participants
[nested] [flat]
* Necessary actions after an OS upgrade
@ 2025-09-30 09:50 Zwettler Markus (OIZ) <[email protected]>
2025-09-30 13:16 ` Re: Necessary actions after an OS upgrade Ron Johnson <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Zwettler Markus (OIZ) @ 2025-09-30 09:50 UTC (permalink / raw)
To: pgsql-admin
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" 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, 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.
Thanks, Markus
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Necessary actions after an OS upgrade
2025-09-30 09:50 Necessary actions after an OS upgrade Zwettler Markus (OIZ) <[email protected]>
@ 2025-09-30 13:16 ` Ron Johnson <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Ron Johnson @ 2025-09-30 13:16 UTC (permalink / raw)
To: pgsql-admin
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!
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-09-30 13:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-09-30 09:50 Necessary actions after an OS upgrade Zwettler Markus (OIZ) <[email protected]>
2025-09-30 13:16 ` Ron Johnson <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox