← Home Reduced AI Bootstrap Bastille + Jails

PostgreSQL Memory Plan

Default local memory backend for Clawdie: PostgreSQL 18 in a dedicated FreeBSD jail named db.

Database: PostgreSQL 18

Jail: db (db.clawdie.si)

Provisioning: thick jail

Default network: shared

Optional later network: VNET

Role: future long-term memory backend

Deferred: pgvector, schema design, embeddings, REST API layer

Why this option

Best fit for FreeBSD + ZFS + jails.
Lower operational complexity than recreating a full local Supabase stack first.
Lets SQLite remain the operational state store while PostgreSQL grows into the long-term memory backend.

Decision: start with plain PostgreSQL 18 and prove service health first. Vector embeddings are deferred until the base service is stable.

Install-time choices

Network profile: shared or vnet
Resource profile: minimal = 1G / 10G / 1 vCPU, balanced = 2G / 15G / 1 vCPU
Restore mode: empty or restore from dump

Recommended first-install profile: shared network, minimal resources, and empty database initialization.

Install plan

Create or prepare a persistent jail named db.
Install postgresql18-server and postgresql18-client.
Enable PostgreSQL in jail rc.conf.
Run service postgresql initdb.
Start PostgreSQL.
Validate local access with psql.
Snapshot before schema and before pgvector.

Thick vs Thin

Use a thick jail for db.
Database service is persistent, so rollback and upgrades should be self-contained.
Thin jails remain better suited to ephemeral worker roles.

Baseline resources

Minimal: 1G RAM, 10G, 1 vCPU
Balanced: 2G RAM, 15G, 1 vCPU

Restore path

Create jail.
Install PostgreSQL 18.
Initialize cluster.
Optionally restore from .sql or custom dump.
Validate local access.
Snapshot.

Expected commands

sudo jexec db /bin/sh -lc 'pkg install -y postgresql18-server postgresql18-client'
sudo jexec db /bin/sh -lc 'sysrc postgresql_enable=YES'
sudo jexec db /bin/sh -lc 'service postgresql initdb'
sudo jexec db /bin/sh -lc 'service postgresql start'
sudo jexec db /bin/sh -lc 'psql -U postgres -d postgres -c "select version();"'

Current Proven State

Now proven on the FreeBSD host: the db jail can be created as a thick VNET jail on warden0 with the explicit gateway flag. The canonical create path is:

sudo bastille create -T -B -g 10.0.0.1 db 15.0-RELEASE 10.0.0.2/24 warden0

sudo bastille create -T -B -g 10.0.0.1 db 15.0-RELEASE 10.0.0.2/24 warden0
sudo bastille config db set host.hostname db.clawdie.si
sudo bastille restart db
sudo jexec db /bin/sh -c 'hostname && ifconfig && netstat -rn'

Important: if the jail comes up with the correct IP but no default route, that is a provisioning defect. The fix is the explicit gateway flag -g 10.0.0.1, not a manual route added after the fact.

ZFS notes

ashift is a pool or vdev decision and cannot be corrected later on an existing pool.
For modern 4 KiB devices, the expected value is usually ashift=12.
Dataset-level PostgreSQL starting settings should be conservative: compression=lz4, atime=off, recordsize=16K.

Snapshot points

Use this naming baseline:

-DD-mon-YYYY-HHMMSS

Fixed month abbreviations: jan feb mar apr maj jun jul avg sep okt nov dec

-08-mar-2026-180000
-ready-08-mar-2026-183600
-schema-08-mar-2026-190000
-pgvector-08-mar-2026-193000

Not in scope yet: copying the old v2 Supabase shell scripts directly. Those are reference material, not the first implementation target for Clawdie.