Record PostgreSQL collation maintenance
GeoIntel CI / docs-smoke (push) Has been cancelled
GeoIntel CI / contract-smoke (push) Has been cancelled

This commit is contained in:
Codex
2026-06-17 06:58:21 +02:00
parent 53bbb45d6b
commit 21b84dae6c
3 changed files with 31 additions and 0 deletions
+22
View File
@@ -1,3 +1,25 @@
## Sprint 37 Tower PostgreSQL collation maintenance (2026-06-17)
Changed:
- Performed the manual PostgreSQL collation maintenance action reported by the live migration smoke on the Tower all-in-one runtime.
- Created a pre-maintenance custom-format database backup at `backups/geointel-before-collation-refresh-20260617-065707.dump`.
- Ran `REINDEX DATABASE geointel;` followed by `ALTER DATABASE "geointel" REFRESH COLLATION VERSION;`.
- Confirmed the database collation metadata now matches the runtime collation version: `geointel stored=2.36 actual=2.36`.
Validation:
- `LIVE_SMOKE_CONTAINER=geointel bash scripts/live_migration_smoke.sh` passed on Tower and reported `Database collation version: ok`.
- `bash scripts/verify_browser_runtime.sh http://192.168.10.150:1202` passed.
- `bash scripts/verify_gis_runtime.sh http://192.168.10.150:1202` passed.
- `bash scripts/verify_demo_export_workflow.sh http://192.168.10.150:1202` passed.
Notes:
- An initial SSH script attempt was interrupted by PowerShell BOM/stdin handling before reindex or refresh executed; the subsequent base64-delivered script ran without `docker exec -i` stdin interference.
- Earlier backup attempts were left in `backups/` alongside the final validated backup.
- No code, API contracts, migrations, product features, provider fetching or AI behavior changed.
Next recommended pass:
- Continue with export/download polish or frontend export center hardening, using the now-clean Tower runtime as the validation target.
## Sprint 32 Unraid all-in-one runtime (2026-06-17)
Changed: