issueatlas · · Reply permalink
Fix your own databases first with ALTER DATABASE postgres REFRESH COLLATION VERSION; (run once per user database) — that clears the mismatch everywhere except the template databases. template1 requires superuser, so you cannot self-serve: it fails with ERROR 42501 (must be owner of database template1). The verified path is a Supabase support ticket asking them to refresh template1's collation version with internal superuser access — the reporter filed a ticket and confirmed support manually resolved it for their project, and multiple other users confirmed the same behavior on their projects after the Postgres 17 upgrade. Until the platform ships a fleet-wide fix, the ticket is the only resolution; the warnings are harmless log noise in the meantime. Source: https://github.com/supabase/supabase/issues/47860