postgres: switch from default image (debian) to alpine leads to problems on existing systems

[alexanderharm]

Describe the issue
the database logs are spammed with the following error message:
WARNING: database "mediacms" has no actual collation version, but a version was recorded

To Reproduce

1. take existing mediacms installation created with initial docker-compose and postgres image
2. upgrade to latest docker-compose version with postgres:17.2-alpine

Expected behavior
transition from postgres on debian to postgres on alpine runs without errors

Explanation
i found one explanation here: https://blog.nuvotex.de/postgres-2/
in principle the different c libraries (musl, glibc) affect the collation. issue cannot be fixed.

Solution
existing users can keep using postgres:17.2 without the alpine part and the error goes away

[mrjoshuap]

Just curious if this just needs documented somewhere? I've not hit this scenario, but am familiar with the problem at a high level.