Missing Indexes & Collation Mismatch after Upgrading to GitLab CE 18.3.3

GitLab CI/CD
1

Hai all

I recently upgraded our instance from GitLab CE 18.3.2 to 18.3.3 to address the security advisory related to a PostgreSQL vulnerability (CVE reported in 16.8), which required upgrading PostgreSQL to version 16.10. After the upgrade, I noticed two new sections under Admin → Database Diagnostics.

After running the checks, I got the following results:

  • Collation mismatches:

    Collation name: default
Stored version: (blank)
Actual version: 2.35

  • Schema health check:
    It shows 12 missing indexes like:

p_ci_pipelines_ci_ref_id_id_idx
p_ci_pipelines_ci_ref_id_id_source_status_idx
p_ci_pipelines_id_idx
...
p_ci_stages_pipeline_id_position_idx

There are no corrupted indexes reported, and GitLab seems to be working fine so far.

My questions:

  1. Is the collation mismatch something that needs action, or can it be safely ignored?

  2. For the missing indexes, is running gitlab-rake gitlab:db:fix_mismatched_schema/sudo gitlab-rake gitlab:db:check
    the recommended and safe way to fix this in production?

  3. Are there any precautions or downtime considerations before running this fix?

Any guidance or best practices from others who’ve encountered this after upgrading to 18.3.3 would be really helpful.

image
image902×841 42.4 KB

Thanks in advance! :folded_hands:

2

As for the collation issue, it says in your screenshot it’s informational and may not be a problem.

3

Thanku