Record PostgreSQL collation smoke result
This commit is contained in:
@@ -1645,9 +1645,14 @@ Tested:
|
||||
- `cd frontend && npm run typecheck`
|
||||
- `cd frontend && npm run build`
|
||||
- `bash scripts/run_readiness_check.sh`
|
||||
- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/deploy_tower.ps1`
|
||||
- `bash scripts/verify_browser_runtime.sh http://192.168.10.150:1202`
|
||||
- `bash scripts/verify_gis_runtime.sh http://192.168.10.150:1202`
|
||||
- `bash scripts/verify_demo_export_workflow.sh http://192.168.10.150:1202`
|
||||
|
||||
Open:
|
||||
- Run the updated smoke against Tower to confirm whether the reused volume still reports a collation mismatch.
|
||||
- Tower live smoke reports `COLLATION_VERSION_MISMATCH: database=geointel stored=2.31 actual=2.36`.
|
||||
- Runtime remains green. The next maintenance action is optional/manual acknowledgement after backup/index review: `ALTER DATABASE "geointel" REFRESH COLLATION VERSION;`.
|
||||
|
||||
Limitations:
|
||||
- The smoke reports and documents the maintenance action. It intentionally does not mutate collation metadata automatically.
|
||||
|
||||
Reference in New Issue
Block a user