Report PostgreSQL collation drift in live smoke
This commit is contained in:
@@ -91,6 +91,22 @@ curl -I "http://192.168.10.150:${GEOINTEL_FRONTEND_PORT:-1202}/geointel-icon.svg
|
||||
curl -I "http://192.168.10.150:${GEOINTEL_FRONTEND_PORT:-1202}/geointel-icon.png"
|
||||
```
|
||||
|
||||
The live migration smoke also checks PostgreSQL database collation metadata.
|
||||
When reusing a PostGIS volume created by an older Debian/glibc runtime, it may
|
||||
print `COLLATION_VERSION_MISMATCH`. This is a maintenance warning, not an app
|
||||
startup failure. Review backups first, then acknowledge the new runtime
|
||||
collation version inside the running container:
|
||||
|
||||
```bash
|
||||
docker exec -it geointel psql -U "${GEOINTEL_POSTGRES_USER:-geointel}" -d "${GEOINTEL_POSTGRES_DB:-geointel}"
|
||||
ALTER DATABASE "geointel" REFRESH COLLATION VERSION;
|
||||
```
|
||||
|
||||
If you rely on text indexes with locale-specific ordering, plan a maintenance
|
||||
window and rebuild the affected indexes before acknowledging the version. The
|
||||
current GeoIntel V1 spatial workflows primarily use UUIDs, JSON metadata and
|
||||
PostGIS geometry indexes, but the warning should still be tracked explicitly.
|
||||
|
||||
## Change the browser port
|
||||
|
||||
Edit `.env`:
|
||||
|
||||
Reference in New Issue
Block a user