fix: make the database disk image 6 GB instead of 2 GB

- VOLUMES["db"] goes from 2048 to 6144 MiB, so every new instance gets a 6 GB database image.
  Instance 4 filled its 2 GB image with analytics logs on 2026-10-14: Postgres crashed and could
  not finish crash recovery without free space. Instance 2 had already been grown to 6 GB by hand.
- Measured on instance 2: about 1.2 GB of logs a day under browser-test traffic, kept for
  LOG_RETENTION (2 days), plus up to 1 GB of write-ahead log. That peaks near 4.5 GB.
- Only instances created after this change get the larger image; existing ones keep their size.
- README disk line, the two unit tests that assert the db volume size, and the version
  (1.6.3 -> 1.6.4 in VERSION, supaspin and README.md) are updated.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This commit is contained in:

Igor K.

2026-10-14 08:46:50 -04:00

co-authored by

Claude Sonnet 5.5

parent da8f02310a

commit b1ae4f1daa

4 changed files with 10 additions and 7 deletions

VERSION

+1 -1

View File

@@ -1 +1 @@
 .6.3
 .6.4