After applying the 2025.10 update to SAS Viya environments that use the internal PostgreSQL database (Crunchy Data), warning messages might occur in PostgreSQL server logs, psql, or other logs that access the database.

Here is an example message:

WARNING: database "postgres" has a collation version mismatch
DETAIL: The database was created using collation version 2.28, but the operating system provides version 2.34.
HINT: Rebuild all objects in this database that use the default collation and run
      ALTER DATABASE postgres REFRESH COLLATION VERSION,
      or build PostgreSQL with the right library version.

Cause

During the Crunchy PostgreSQL for Kubernetes (CPK) upgrade from version 5.7.5 to 5.8.3, the underlying Universal Base Image (UBI) changed from Red Hat Enterprise Linux 8 (RHEL 8) to RHEL 9.

This upgrade updated the glibc locale data, which results in a collation version mismatch for the postgres and template databases included with the Crunchy installation

Impact

• The warning messages are benign and do not affect SAS Viya operation or data integrity.
• Normal database operations continue without issue.
• You can safely ignore the messages.
• An automatic fix to remove the warnings is planned for the 2025.11 release.
• Only updated deployments (from earlier SAS Viya releases to 2025.10) are affected. New 2025.10 installations do not generate these warnings.

Workaround

If you want to remove the warning messages before the 2025.11 release, you can manually run Kubernetes jobs that refresh database indexes and vacuum operations.

During the update process, cronjobs for the PLATFORM and CDS databases are created but not scheduled to run automatically.

You can manually create jobs from these cronjobs by running the following commands.

For the PLATFORM database:

kubectl -n <namespace> create job sas-postgres-reindex-vacuum-job-platform \ --from=cronjob/sas-postgres-reindex-vacuum-cronjob-platform

For the CDS database (if installed):

kubectl -n <namespace> create job sas-postgres-reindex-vacuum-job-cds \ --from=cronjob/sas-postgres-reindex-vacuum-cronjob-cds

After running these jobs, the warning messages will no longer be displayed in the PostgreSQL logs or other related SAS Viya logs.

Additional Information

• This issue is specific to environments that use the internal PostgreSQL (Crunchy Data) database included with SAS Viya.
• External or customer-managed PostgreSQL instances are not affected.
• The automatic correction will be included in the 2025.11 update.